Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2006

    Unanswered: Order of fields in a DBF

    I was curious if this is sometimes important in an application.

    I have 2 DBF's of identical structure but a different field order. Are there any times that copying them into an application can create a problem.


  2. #2
    Join Date
    Dec 2003
    Nope. If you do a REPLACE, GATHER, or whatever to update the table, it goes by field name.
    The only time it could matter is if you start referencing the fields by field order rather than name.

    Even more Fox stuff at

  3. #3
    Join Date
    Feb 2005
    The field order can be important depending how the program addresses the data. As DSummZZZ noted that as long as you reference just the field names it doesn't matter, but depending how your app is structured you may be running something that references the field order. I have an app that has a filter built into the various interfaces so that the user can filter a view, doc, or report to include only the records needed. This interface has valid's & descriptions that are based on DBF order.

    Your need to understand how your program uses the data in all of the code to understand whether that is going to be a problem or not. Does the program import data from and ASCII file? A number of different processes may use the data different ways.

    Jim C.

    The other thing is that a index is better off if the key fields are at the top of the structure. Everything is better faster & quicker.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts