Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Update failed on TABLEUPDATE
Message
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows Server 2003
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01456746
Message ID:
01456763
Views:
69
>I have an app that updates some VFP tables separately from a main app that the users normally use. It runs all day on a Win2K3 server. It opens all the files shared, as does the main app. It will run fine for awhile, but then will start failing on the TABLEUPDATE command (all tables I'm updating are opened with table buffering). I have used AERROR after the table update to see what the issue is and what it gives me is an error 1099 Procedure Canceled. Not real helpful. There is no 1099 error listed in the VFP help. It seems that 1099 is associated with the VFP OLE driver. I'm accessing these tables directly via VFP, so I don't see how that would come into play. I'm wondering if it could be something in the RI code and have considered changing to the data-driven code that comes from the MegaFox book (or wherever it was - can't remember which book it was right now). I think Doug Hennig has some, too. Previously, I was having a different issue, but seem to have gotten around that. One of the tables would not open, giving me an error 108 File is in use by another user. Again, all the tables are opened in shared mode, so I was unclear why that was happening. I was unable to determine what was causing that, but since I was opening the tables as needed and closing them after use, I decided to leave the two tables that were causing this issue open all the time. That seems to have fixed that problem, but now I'm getting the failed updates with the 1099 error. Does anyone have any suggestions about how I might address this?
>
>Thanks,
>
>Russell Campbell

Procedure cancelled can come from a trigger (RI, you're correct). We had these errors. You may want to dive deeper into the trigger's code.
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