Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Cursor fields being truncated at runtime
Message
From
19/01/1999 20:56:55
 
 
To
19/01/1999 19:49:04
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00177621
Message ID:
00177862
Views:
26
>>>
>>>Also, rather that using AFIELDS, you could
>>>SELECT * FROM tablename INTO CURSOR cursorname NOFILTER
>>>to get a copy of your original table for reporting.
>>
>>You raise an interesting point here Mark. That sure is a way to create a cursor based on an existing structure. The cursor will contain every record in the original dataset. I often want an empty cursor.
>>You could go
>>SELECT * FROM tablename WHERE .F. INTO CURSOR cursorname NOFILTER
>>however this is not Rushmore optimizable (try it on a huge dataset!)
>>So....
>>Does anyone know a fast one liner for creating an empty cursor based on an existing structure?
>
>Just an interesting tidbit here- when you open a view with the NODATA clause, internally, VFP uses an SQL statement like the following to return an empty cursor:
>
>SELECT * FROM MyTable WHERE 1=0
>
>I learned this on accident when a my error handler trapped the incorrect executing line of code, and this showed up.

Hi Eric,
I just did some timing tests on this one and it runs same time as 'WHERE .F.', but strangely it appears to be fully optimised, and so does 'WHERE .F.'.
Perhaps FPW2.6 didn't optimise these things but VFP does ???
FWIW .F. is a little faster than 1=0 on my setup.
Previous
Reply
Map
View

Click here to load this message in the networking platform