Wrong record order in Form
- Thread starter djchapple
- Start date
boblarson
Smeghead
- Local time
- Today, 10:53
- Joined
- Jan 12, 2001
- Messages
- 32,040
FYI -
Tables do not store the data in any particular order and you need to use a query with an order set to what you want in order to have an order you want. Normally a table view will display tables in the primary key order if a primary key is defined, but it is not necessarily going to stay that way.
And you should never rely on the "Record Number" (that thing in the navigation of a form) as it is all relative. It is ONLY valid for the current recordset that the form has and when requeried or the form closed and reopened, it can be in a completely different order (unless the underlying recordset is ordered) And even then if records are added/deleted it will affect which number shows up for which record.
So, you need to have a primary key assigned to the table (an autonumber is a good one) and even better for ordering, if you want the order in which the records were entered, is a date/time stamp.
Tables do not store the data in any particular order and you need to use a query with an order set to what you want in order to have an order you want. Normally a table view will display tables in the primary key order if a primary key is defined, but it is not necessarily going to stay that way.
And you should never rely on the "Record Number" (that thing in the navigation of a form) as it is all relative. It is ONLY valid for the current recordset that the form has and when requeried or the form closed and reopened, it can be in a completely different order (unless the underlying recordset is ordered) And even then if records are added/deleted it will affect which number shows up for which record.
So, you need to have a primary key assigned to the table (an autonumber is a good one) and even better for ordering, if you want the order in which the records were entered, is a date/time stamp.
