Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Update Conflict nightmare
Message
De
13/02/2001 19:36:03
 
 
À
13/02/2001 18:25:57
Adam Skowronski
Custom Designed Systems
Miami, Floride, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00474619
Message ID:
00475531
Vues:
47
>>>>>>>>>>>>>>>>>>
Alex, the system you mention for assigning the ID's is just what I have in place and have had since we worked together at Pegasus. It has worked just fine all these years, both in DOS (you remember that), and recently for me, in VFP. It is just this year that I am having this problem, ever since the customer changed over to NT from a Novell network. The code hasn't changed.
>>>>>>>>>>>>>>>>>>

I don't even remember my name some mornings! So I didn't remember that you were using that scheme since FPD's days. <g>


>>>>>>>>>>>>>>>>>>
What is happening is that both users on the network are getting the same number, even though the table was locked with FLOCK(). This is where I am bewildered. There was another thread having the identical problem. I received a reply from Thomas Martin, telling me about similar problems with NT and the Oportunistic Lock settings. I have the customer checking this out and will post what effect it has.
>>>>>>>>>>>>>>>>>>
I'm not sure what is causing the problem. FLOCK() should've prevented that. Of course, now that you are changing to buffering it should only improve. I'm not familiar with the differences in locking schemes between Novell and NT to even guess.


Alex Feldstein, MCP, Microsoft MVP
VFP Tips: English - Spanish
Website - Blog - Photo Gallery


"Once again, we come to the Holiday Season, a deeply religious time that each of us observes, in his own way, by going to the mall of his choice." -- Dave Barry
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform