The lock timeout occurs when the BDE fails to get a lock. So its instant 
by default right now as there is no retry. I am sure this was not the 
case way back, but maybe I am thinking about pre-idapi Paradox Engine.

By setting a retry amount, the lock timeout would occur after that time 
has elapsed.

So, I am wondering if when a mapped drive goes to sleep, this retry 
amount would allow the drive to reawaken. Also if WiFi is involved if it 
would be more forgiving.

When I get time I will try a few tests (such as unplugging the network 
cable) to see what happens.


On 5/06/2021 2:05 AM, Steven Green wrote:
> so what's triggering the lock timeout? 30 seconds?
>
> --
>
> Steven Green
> Myrtle Beach, South Carolina, USA
>
> http://www.OasisTradingPost.com
>
> Collectibles and Memorabilia
> Vintage Lego Sets and Parts
> - and Paradox support, too
> "Leslie"  wrote in message news:60b774ce$1@pnews.thedbcommunity.com...
>
> I think I may have posted this info some years ago but I cant search it.
> Anyways, I just came cross it again and thought it would be good to
> place it here for anyone that needs the info....
>
> In the old days I am pretty sure the timeout to retry to get a lock was
> about 3 seconds but at some point that changed and even though the BDE
> help file says it is 5 seconds by default, it is in fact wrong and there
> is no retry attempted.
>
> So you can force the retry count by calling dbiSetLockRetry(5) which is
> for the current BDE session. I am unsure if Opal has an equivalent
> function.
>
> Here is a discussion, I am sure there were more but it looks like the
> internet is getting cleaned over time:
> http://www.delphigroups.info/2/fb/343380.html
>
>
>
>
>

-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus