Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Determining Cause of Update Conflict
Message
From
21/08/2001 08:51:01
 
 
To
21/08/2001 08:41:25
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00546646
Message ID:
00546657
Views:
23
Than I cannot add anything to what you know. Just make views carefully. With SQL Server aerror() helps a lot to see errors on SQL Server. With VFP - I don't know.

>Hey Vlad,
>
>Been there... All it returns is a bunch of NULL expressions and "Update Conflict" in the result array.
>
>Renoir
>
>>Hi!
>>
>>Try to use aerror() function just after error message appeared.
>>
>>HTH.
>>
>>>I know to look towards keys, etc when there is an Update Conflict error, but is there anything more descriptive that points to what is actually causing the conflict to narrow down the search? If it knows enough to return the error, it must know what the cause was. What a great help if it would pass that along to the developer. Is there a way already? Thanks!
>>>
>>>Regards, Renoir
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.com
ICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs

It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.
Previous
Reply
Map
View

Click here to load this message in the networking platform