>>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 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.

That's understandable and valid. Now that might be a nice little item for an enhancement. Be able to specify the order the fields appear in the DE.

>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.

Mmmm...I'm not sure I completely understand this, so take the following with a (very large) grain of salt

lctable = DBF()
lcalias = ALIAS()
= AFIELDS(a_fields)
= ASORT(a_fields)
CREATE CURSOR Whatever FROM ARRAY a_fields
USE IN (lcalias)
APPEND FROM (lctable)
COPY TO...

That's put the fields in alphabetical order. Or are you talking about something else?