Jim,

While it may be a clue as to design problems, I know that I like to keep "logically related" fields together as much as possible. So, for instance, when it was discovered that "County" was now a required field for some future processing in a small system of mine I put the "County" fields (home address, business address, ship to address, etc) right between their respective Town/City and Province fields. And I got real peeved when a browse would show them at the end. Turned out they were exactly where I had wanted/put them and it was Browse that was doing its own thing. When I deleted specific records in FoxUser all was now how I had wanted it when I Browsed.



>Ron,
>
>I would suggest that you rethink what you are doing. The fact that you care about the physical location of the field in the structurte of the data table is a clue that something is wrong in your design.
>
>If you need fields in a certain order for a certain operation you can always use SELECT to reorder the fields for that operation.