Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Record is out of range
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01173246
Message ID:
01173338
Views:
8
Ok, I think the problem is in using non structured indexes.

Somehow this command
IF NOT USED("Sum_Commission")
	USE Comision again alias Sum_Commission in 0 INDEX com_inv
ENDIF
changes order in already opened Comision. I guess you can not use the same table twice with the same Index file.

I think I may better try the array solution then.

>Hi again, Naomi.
>
>>Thanks a lot for your reply.
>
>You're welcome :^).
>
>>This is actually not my code, I'm just trying to make it work.
>
>Okay. Let's see if we can make that happen :^).
>
>>Basically, originally the table is in particular order and it's scanned
>>while code = lcCode FOR some criteria.
>
>Gotcha.
>
>>In the middle of the scan loop there is another procedure called that sums
>>records from the same table using different order.
>
>Okay. As I'm sure we're both well aware, this is going to change the record
>pointer, and this is why you save it, of course :^)
>
>>Then I restore the order and the record pointer.
>>
>>However, I found, that my table doesn't have an order set at the moment of this error,
>>which is strange, since I have SET ORDER TO 1 in the loop...
>
>Hmmm. Are you setting the INDEX before you call SCAN? Also, I'm
>starting to wonder if the SCAN call doesn't like the ORDER being
>changed on the fly.
>
>Just out of curiosity (and if this is possible without a big rewrite),
>set the NOOPTIMIZE flag in the SCAN call and turn off all indexing <g> and
>tell us if it works.
>
>I'm starting to wonder if it's a corrupt index....
>
>Regards,
>
>Randall
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