Erik,

>>The order of the fields shouldn't ever come into play. So it shouldn't make a difference. I'm not terribly familar with SQL Server, but I think I've heard that you can't insert a column into a table without completely re-building the data structure from scratch in that environment.
>
>You're right, field order should never come intoplay in an application, but keping the fields in alpha order (or some other intuitive order) can sure make

I disagree. If you want to create an SDF file, you use
COPY TO ... TYPE SDF (or something like this, don't remember exact syntax right now). The fields MUST BE in a right order. It's important for our customers, at least. It's also important, if you want to convert this file back in DBF. You create an empty shell, then APPEND FROM, right? Now imagine, that if you have your SDF file in different fields order...

life easier for a developer when munging data and dropping fields on a form. I have a fully normalized table or two with 50-80 fields, and keeping the fields in order is important to my productivity.
>
>I don't share Nadya's frustration with the mover list, because I never need to move more than one field at a time, but I do have my own complaint:
>
>There is, AFAIK, no way to programmatically change a field's order in the field list. You have to use the designer.

Share your fillings...