For some reason it is telling me that entries entered on the 18th came before entries entered on the 14th? Seems to me that it has nothing to do with your field being indexed, but how your recordset is sorted.
If you have a "requery" command, that will for sure re-sort your recordset and produce the results you are getting.
I have written a VB application which reads/writes records to ACCESS 2000. When I "movelast", "addnew", "update", then "moveprevious", I expect to see the record which I have just entered. If I open Access and look at the table, it appears that my record was appended to the end of the table, but when I actually navigate through it, Access odviously orders it differently.
However, the record which I just entered is placed somewhere in the middle of my table?! The only field I have indexed is my date/time field.
Field and Table are one you want to update, Update To is the new value you want to put.
Click on the Run button to run the Query, now David’s salary is updated to 11000.
Suppose we have created a table called employee_tbl, now we want to update David’s salary to 11000.
Here is a summary of the major objects in an Access database; Table is an object that is used to define and store data.
When the record is accessed again, the Date Modified field will contain the date and time of the last modification.
You can query that field to determine which records have not been updated within the last six months.
If you remove the WHERE statement, all records will be updated.
But in particular the Sub Datasheet Name property set to nothing can be a problem as it appears Access 2000 will default this value to [Auto].