Saving values for re-use - Access 2000

  • Thread starter Thread starter Leonard Priestley
  • Start date Start date
L

Leonard Priestley

I have two situations where I would like to save a setting so that it is
available the next time the program is run. Firstly, I would like the user
to be able set a default path (images, exporting docs,etc.) which will
operate until the user decides to change it. Secondly, I would like the
user to be able to open the program and find that the current record is the
one last worked on (which I presume means saving the bookmark).
Obviously, I could create a simple table to save such items, but I wonder if
there is another, more elegant way of doing it. I don't know why, but I
feel that using a table for this purpose is probably not how you're intended
to write a database.

Leonard Priestley
 
A table for the config data is the simplest approach.

This article explains how to set the table up, and have your form re-load
the record that was showing last time:
Return to the same record next time form is opened
at:
http://allenbrowne.com/ser-18.html

(It would also be possible to create a custom property on the form if you
prefer.)
 
there is another, more elegant way of doing it. I don't know why,
feel that using a table for this purpose is probably not how you're
to write a database.
Click to expand...

:~) One of the primary ideas of a 'relational' database
system is that you use the database to store information
about the database.

In Access 2.0, the queries where stored in the database: the
tabledefs where stored in the database: the menu customisation
was stored in the workgroup database: the user names where
stored in the workgroup database: the Access Basic modules
were stored in the database: etc etc.

Access has drifted away from that ideal since then, but that
is probably because of input from people who had other priorities.

(david)
 
Back
Top