To late I have alredy figured it out. It all has to do with the COLLATE clause. Defautl on VFP is MACHINE. Once I introduced COLLATE "GENERAL" to my index statement as in
INDEX ON UPPER(manufacturer) TAG manufact COLLATE "GENERAL", then <NONE> showed at the top all the time. The COLLATE clause will NOT affect the existing COLLATE setting.
My reason was to ensure that the users never selected <NONE> or just selected the 1st in the list.
Now I have a better solution that stuffing a blank infrom of the <NONE>
Main Topics
Browse All Topics
by: jrbbldrPosted on 2009-04-13 at 08:35:57ID: 24130502
You are asking "why can't language A work just like language B?"
SQL Server and Visual Foxpro are like apples and oranges - they both share quite a few commonalities, but they are indeed different in a number of ways.
Since you talk about how you can work around the issue, I assume that you are populating the <NONE> value into the intended field. As long as you aware of the issue, then you can easily and knowingly work around it.
You haven't told us which order you prefer - SQL Server's order or VFP's order.
Regardless, VFP's index expression works with character values on the ASCII value of the character values. You can always make a more complex Index Expression incorporating commands such as the IIF() command to get the resultant order the way you want it.
Good Luck