What do you think about tables in front end?

[Gntlhnds]

I have a database that I have split. I did leave three tables in the front
end, though. One table stores the password for the database (low security, I
know), the other stores the switchboard information, and another stores a
flag for a splash screen (to prevent it from showing everytime a user opens
the database). The database I've created I'll be giving to people and they
will place it either on their computers or on their servers. I won't have
access to any of their databases after that. I split it so that I can make
design changes and then send them the updates. Is it a good idea to have
these tables in the front end? I put a button on the switchboard so that the
users can refresh their links once they get the database and I also am tying
it into the splash sceen (once the splash screen closes it runs the code to
relink the tables, and if they have opted to not see the splash screen
anymore, it won't ask them to refresh the links either). I didn't want to
set up the database to automatically refresh the links every time the user
opens the database because they shouldn't lose their links at all, it's just
something that may need to be done every once in a while just in case. Does
this sound good to you guys, or is there a better way of doing this? This is
the first database I have designed, so I would appreciate some good ideas.

 

[Rick Brandt]

I have a database that I have split. I did leave three tables in the
front end, though. One table stores the password for the database
(low security, I know), the other stores the switchboard information,
and another stores a flag for a splash screen (to prevent it from
showing everytime a user opens the database). The database I've
created I'll be giving to people and they will place it either on
their computers or on their servers. I won't have access to any of
their databases after that. I split it so that I can make design
changes and then send them the updates. Is it a good idea to have
these tables in the front end? I put a button on the switchboard so
that the users can refresh their links once they get the database and
I also am tying it into the splash sceen (once the splash screen
closes it runs the code to relink the tables, and if they have opted
to not see the splash screen anymore, it won't ask them to refresh
the links either). I didn't want to set up the database to
automatically refresh the links every time the user opens the
database because they shouldn't lose their links at all, it's just
something that may need to be done every once in a while just in
case. Does this sound good to you guys, or is there a better way of
doing this? This is the first database I have designed, so I would
appreciate some good ideas.

Front end tables of the sort you describe are fine and common. Many lookup
tables that will remain static or will only change when you issue front end
updates will also be correctly placed in the front end file.

 

[Gntlhnds]

now when I send an updated front end, it will have new tables, which will
replace the table that has their password on it. anyway that when I send an
updated front end that it will automatically keep the table from the original
front end that stores the password?