Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Should I allow time for USEing a table?
Message
From
17/04/2008 19:14:51
 
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01311596
Message ID:
01311597
Views:
21
There could be many things happening. Is the header being locked? Or the database? Do you use transactions? Are you using buffering? Is exclusive off? Are these free tables? You can try something like in the message below and see if it makes a difference and then, if not, proceed from there:

Re: Attempting to lock Thread #1282563 Message #1282736

Also check this:

Re: Error 108: What gives? Thread #1175426 Message #1175580

It would be better if you could post more information on the method you currently use for opening and editing a record in a table.


>Hi,
>
>A customer says that every so often they get an error message 108 File is in use by another user. I suspect that the server where data reside could be causing the problem. Maybe, another user on another application is attempting to read or write. I don't know. But I was thinking to set a timing loop when USEing (opening) a table to allow for, say, 5 or 10 seconds. Currently, my code simply attempts to open a table once and if it fails, reports a problem.
>
>Is it a good design practice to allow some time for a table to be opened?
.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform