Why not write user preferences to the registry. You could use the table
to supply the initial default values, but it's simple to save user options
with the SaveSetting and retrieve them with the GetSetting calls.
Note: gcstr_Client is a global variable with my app name.
SaveSetting gcstr_Client, "Attributes", "AccessLogin", pstrSUser
SaveSetting gcstr_Client, "Attributes", "AccessLevel", bytBLevel
SaveSetting gcstr_Client, "Attributes", "Tip of Day", lngX
SaveSetting gcstr_AppName, "Options", "Startup Form", Me.fraStartupForm
lngX = GetSetting(gcstr_Client, "Attributes", "Tip of Day", -1)
Me.chkLinkLocal = GetSetting(gcstr_AppName, "Last Values", "Link Local", -1)
lngStartup = GetSetting(gcstr_AppName, "Options", "Startup Form", 1)
As for having the bound form open, I'm not aware of a problem with that.
In fact, keeping a table open in Access 2000 speeds up access, as the user
maintains a foot-hold on the ldb file.
However, if every user has it open and is making changes to the table, that
might cause a problem.
--
Danny J. Lesandrini
dl*********@hotmail.com http://amazecreations.com/datafast/
"WJA" <WJ****@hotmail.com> wrote
I have a database that has a "settings" form that is always open and
hidden unless an "Admin" user chooses to view it. The form is bound to
a "settings" table that has one record and several fields related to
the settings on the form. I use the info on the "settings" form to set
the way that other forms behave when they are opened.
The database has a handful of users and the "settings" table is being
corrupted on a regular basis. I have narrowed the problem down to one
user but so far the IT department is unable to pinpoint a problem with
their PC or network connection.
My question is: is it bad practice to have a bound form open at all
times and am I asking for trouble by doing this?
Any help is appreciated.