re: #222 Walter L. Newton

It really depends if she was using a simply written Access application or some custom piece of Access software where the programmer is handling commits the database themselves.

If you simply create an Access table, and let Access design a data entry screen around that table, Access will also automatically include code that will write data directly to the table, almost in realtime, the actions you are describing above.

But if a programmer wants to control the data themselves, they can set up buffers and cursors where the data is stored (in memory so to speak), issue hard commits when the programmer wants the data to be flushed to the table and set up roll back points, so the data does not get written to the table and the table reverts back to a certain condition at a certain set point.

So, the answer to this question is more dependent on how Access was being used… a down and dirty data entry tool or as a full blow programmer designed application where the programmer coded in how the data is moved, from entry to a hard flush to the disk.

FYI.

One article I recall said she was using Lotus, and that she was the only one in the office still using it. Don’t have it handy, could be mis-remembering it, but I thought I’d toss it into the discussion.