• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

Moving Fields

You might want to move a field in a table definition for a number of reasons. Perhaps you made an error as you entered or changed the information in a table. Or perhaps you’ve discovered that you’re using some fields you defined at the end of a table quite frequently in forms or reports, in which case it would be easier to find and work with those fields if they were nearer the beginning of your table definition.

Inside Out: Is the sequence of fields in your table important?

The actual sequence of field definitions in a table is not all that important. In the relational database model, there really is no defined sequence of fields in a row or rows in a table. Microsoft Access, like most databases that implement the relational model, does allow you to define a field order when you create a table. This order or sequence of fields becomes the default order you see in a table datasheet or in a list of field names when you’re designing a query, form, or report.

I like to at least group fields together in some reasonable order so they’re easy to find, and I like to place the primary key fields at the top of the list. There’s really no hard and fast rule that you must follow for your database to work efficiently.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint