Microsoft Access Database Architecture: Storing Temporary Data and User Settings

Read our new paper on:

Microsoft Access Database Architecture: Storing Temporary Data and User Settings

There are many things a user does with an application that need to be preserved either during processing, between screens, between sessions, or between application updates/versions. When designing a system, it’s important to consider what needs to be kept and where/how to do this. If designed properly, the data should also support multi-user environments.

Problem

Users are commonly annoyed to be forced to re-enter their last specifications when the application should start with that as its default. After all, a computer is supposed to be good at remembering things, right?

Solutions

There are several ways to preserve user information during a session, on a PC, and/or between PCs:

  • Keeping Selections in Memory for the Current Session
  • Using the Registry to Store User Information Between Sessions
  • Using Private Tables to Store Information Between Sessions
  • Making Sure Previous Values Remain Valid

Read the paper for more details and tips.