Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Check for uniqueness - what's the problem in this code
Message
 
 
To
02/05/2002 11:04:37
Walter Meester
HoogkarspelNetherlands
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00651801
Message ID:
00651944
Views:
17
>Hi nadya,
>
>I don't quite understand what you're doing here, but I guess it could be concurrency (multiuser) problems.
>
>The select statement uses OS level buffered data when it can. It does not ensure that it uses the most recent data on the network.
>
>Before checking for uniqueness, the involved table must be (file)locked in order to get the most recent data from it.
>
>Walter,

Hi Walter,

The appender application could be run by only one user. I don't use buffering at all for this particular application.

Do you think, it could be some internal NT buffering, which causes this select to return incorrect results?

So, do you suggest to open BatchCntrl table exclusively before running this select statement?

This is all very weird...
If it's not broken, fix it until it is.


My Blog
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform