Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Lock-up using LOCATE or SCAN
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00096380
Message ID:
00096406
Views:
12
>I have an table with buffering set to 5 (optimistic table), which I wish to SCAN through and change some records. When I attempt to do this, VFP locks up on the following command:
>
>LOCATE FOR MYTABLE.nForeignKey = lnForeignKey
>
>I have a SCAN loop following the LOCATE which includes the same FOR condition, plus a couple other conditions. If I comment out the LOCATE, the SCAN statement locks up just as the LOCATE did.
>
>Here are the conditions under which this operating:
>
>1. I'm using VFP 5.0a with Service Pack 3, under Win95 (OSR1) on a local hard drive.
>2. There is a BEGIN TRANSACTION in progress.
>3. I did a SELECT MYTABLE immediately prior to the LOCATE.
>4. Some records in MYTABLE have already been edited, but issuing TABLEUPDATE(.T.) prior to the LOCATE makes no difference.
>5. lnForeignKey is a LOCAL variable, but declaring it PUBLIC makes no difference.
>6. Running COMPILE CLASSLIB and PACKing the class library in which the code resides makes no difference.
>7. Reindexing and packing the table (using Stonefield Database Toolkit) makes no difference.
>8. VALIDATE DATABASE made no difference.
>
>At this point I'm totally mystified. Any thoughts on this would be greatly appreciated.
>Thanks,
>Mike
Have you visually inspected the data itself? We had a problem similar to that and it turned out we had 'garbage' in a couple of fields.
"You don't manage people. You manage things - people you lead" Adm. Grace Hopper
Pflugerville, between a Rock and a Weird Place
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform