Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is this an intended behavior or is a bug?
Message
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Is this an intended behavior or is a bug?
Miscellaneous
Thread ID:
00752429
Message ID:
00752429
Views:
45
Consider this

With a table named mytable that has character, numeric, logical and memo fields
cSQL = “SELECT * DISTINCT FROM mytable where field1 like ‘%hello%’ INTO CURSOR myquery”
&cSQL
in this case field1 is a character (50) field.

It works on VFP 6 and 7 but in VFP8 it returns error 34 on the &cSQL line

After toying with it a little I found that removing the clause DISTINCT from the command it works just fine in VFP 8
cSQL = “SELECT * ROM mytable where field1 like ‘%hello%’ INTO CURSOR myquery”
&cSQL
So the questions are:

Is this an intended behavior or is a bug?

If it is intended how to avoid duplicate records on the result query?

This was run under win2k with PIII 800 mhz and 500mb ram and the only applicatin running was VFP.
B.D.H.
Next
Reply
Map
View

Click here to load this message in the networking platform