Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Aerror() returns unexpected results
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00080556
Message ID:
00080813
Views:
29
>I am still a little confused though. In the VFP manual and other VFP books, I see the reference to the error returned by aErrors() of 1700 which states it is a record locking problem, but I can't find error 1700 in VFP help. Is 1700 and 109 the same error? and when I have a record locking problem during my update using the aError() function, why does it return the error of 109 instead of 1700?


John,

There is no error 1700 in VFP. The error codes that apply to a failed update besides 1585 Update conflict are;

3 File is in use
108 File is in use by another
109 Record is in use by another
130 Record is not locked
1502 Cannot write to record becasue it is in use
1503 File cannot be locked
1705 File access denied
1709 Database object is in use by someone else

You got error 109 because the record was locked by some other user or form.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform