Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Line too long on ZAP?
Message
From
28/10/2008 11:10:47
 
 
To
28/10/2008 11:01:46
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Vista
Network:
Windows 2008 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01357639
Message ID:
01357708
Views:
25
OK, I can see how there would be a problem with re-creating an index for zero records if TRIM were part of the index expression. I learned a long time ago not to do that. Nor are the field names reserved.

In any case .... it seems like simply removing all tags and filters before the ZAP eliminates the problem anyways.

Thanks,



>>Nope, I don't ever do that.
>>
>>And, even if I did, I would have a hard time seeing it's relevance to a ZAP. Or why that would cause the error message "Line Too Long".
>
>Well, what IS the index expression? And the filter expression? You may want to rename fields, if the are incriminating (grin), but watch that the field names themselves are not reserved words.
>
>I suspect that after doing the ZAP, Visual FoxPro will have to re-create the index - for zero records. And, if there were an expression with alltrim(), that would immediately cause an error (because of the zero-length string), which might not appear when there are actually some records.
Jim Nelson
Newbury Park, CA
Previous
Reply
Map
View

Click here to load this message in the networking platform