Delay 1 -5 seconds when read from linked table

[CJ_London]

did you also modify the refresh rate (per post #2) to perhaps 1 second?

[KoMiKo]

Yes, but did not help - see post #3

[CJ_London]

You've used 30 seconds - I was suggesting 1

[darkwind]

I'm skeptical that you could get the kind of performance gains you're looking for, but you could try looking into the ACE registry keys. SharedAsyncDelay and FlushTransactionTimeout are of particular note.

See here: http://casadebender.com/reference/ot...ers/ba13_2.htm

You can set these values at runtime using the DBEngine.SetOption method: https://learn.microsoft.com/en-us/of...ion-method-dao

[KoMiKo]

You've used 30 seconds - I was suggesting 1

According to your suggestion in #2: "...you need to reduce the refresh interval..." I used 1sec.
Now I changed also OLE/DDE timeout to 1sec, but no success. According to this info: https://support.microsoft.com/en-us/...d-595d179a9cbb, this settings will not help.
But I appreciate your effort, thank you.

[KoMiKo]

I'm skeptical that you could get the kind of performance gains you're looking for, but you could try looking into the ACE registry keys. SharedAsyncDelay and FlushTransactionTimeout are of particular note.

See here: http://casadebender.com/reference/ot...ers/ba13_2.htm

You can set these values at runtime using the DBEngine.SetOption method: https://learn.microsoft.com/en-us/of...ion-method-dao

I found this setting in the documentation

...The PageTimeout setting determines how long Microsoft Jet waits before checking to see if other users have made changes to the database....The default PageTimeout setting is 5,000 milliseconds....

I decreased PageTimeout to 100 ms:

DAO.DBEngine.SetOption dbPageTimeout, 100

The code must run at the very start of app. AND IT WORKS, BINGOO!!! I got a practically immediate response.
Maybe there is more to play with those settings, but even this one setting did the job!

Thank you.