Chip,

I have done some tests without result, in my system I not have the same issue. The configuration is a 4D SERVER and Two clients. The plausible case is that the record is locked, and when the record is unlocked, all work normally.

Thanks

Ferdinando

Il 24/07/19 22:51, Chip Scheide ha scritto:
Ferdinando,
the test I outlined below will test this scenario
the 2 processes represent 2 users.
this test scenario is roughly equivalent to the the situation for live
system with 2 users; and it allows **you** to test the situation, in
the office, on your development system rather then going to the users
site for an indefinite time to wait/try to replicate the error.

On Wed, 24 Jul 2019 22:32:39 +0200, stardata.info wrote:
Chip,

The situation is this:

1 - Client_1 create the record.

2 - At the same time, Client_2 run a loop process every two seconds,
that search if there are new records using QUERY command.

If there are new record, Client_2 do:

SELECTION TO ARRAY([TABEL];Array)

ON ERR CALL ("ERR_MANAGER")

CREATE SELECTION FROM ARRAY([TABEL];Array)

ON ERR CALL ("")

At this point i have -10503 error.

Later wiht the same record number that give -10503 error, ( i know it
because i write a log ) everything works without error.

Thanks

Ferdinando

Il 24/07/19 22:10, Chip Scheide ha scritto:
Ferdinando

to test:
in one process: create (or edit) a record
in a second process: put the record number of the new/edited record
into an array
and create selection from array

if you get the error then this is the problem,
you might be able to catch the error with an On Err Call method.
If you do not get the error - then I would run MSC and repair the data
file.

Chip
---------------
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to