Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Set EngineBehavior 90 - Possible Bug
Message
From
28/03/2005 14:47:07
 
 
To
28/03/2005 14:29:02
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Network:
Windows XP
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00999370
Message ID:
00999517
Views:
17
I must agree with you, Fabio, that considering the input table(s) field names when an ORDER BY is specified is pointless when it is stipulated that any field named in an ODER BY must be in the select's OUTPUT. Clearly it is the OUTPUT field names ONLY that matter.

I also wish that VFP would get rid of it's unhelpful means of determining an output field's size by using some occurrence of its CONTENT and just use the defined field's size unless overridden in the select itself.

cheers

>>Hi Jarid,
>>
>>Sergey is correct, this is not a BUG.
>>
>>Thanks,
>>Aleksey.
>>
>
>Aleksey,
>
>If in the grouping case ( DISTINCT or GROUP BY )
>it is not possible to order to the results for a tablesource's field,
>why VFP search the ORDER BY name in the list of the fields of the table source?
>It does not have sense.
>This creates alone problems in the construction of the query, without benefits.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform