Missing Tables - Access 2000

[cmcmillan]

Hello folks. I have a database with about 10 users. On startup of the
front end (Which holds some tables, macros, forms) I am running a macro
that deletes a couple tables and imports replacements from the back
end, so I can update employee lists at the back end instead of on each
users machine.
What's happening is about once a week or so (3 times so far this week)
my users will try to load their front end and one of those tables is
just plain missing, which throws error messages and halts everything
since the macro can't find the table to delete.
I've got four different databases used for different purposes, but all
of them do pretty much the same thing on startup, but it's only an
issue on this one. Anybody have any ideas what would cause this,
beyond user error (which is certainly a possibility.)?

[Justin Hoffman]

<cm*******@rccl.com> wrote in message
news:11*********************@o13g2000cwo.googlegro ups.com...

Hello folks. I have a database with about 10 users. On startup of the
front end (Which holds some tables, macros, forms) I am running a macro
that deletes a couple tables and imports replacements from the back
end, so I can update employee lists at the back end instead of on each
users machine.
What's happening is about once a week or so (3 times so far this week)
my users will try to load their front end and one of those tables is
just plain missing, which throws error messages and halts everything
since the macro can't find the table to delete.
I've got four different databases used for different purposes, but all
of them do pretty much the same thing on startup, but it's only an
issue on this one. Anybody have any ideas what would cause this,
beyond user error (which is certainly a possibility.)?

Why do you bother doing this at all? Normally you should store all the data
in the backend and have linked tables in the front end which link to the
real back end data. The only time you might decide to have local tables is
to try and get a performance improvement when the data is very static. Even
then you have to weigh that against the hit you take in keeping the tables
synchronised. By what you state, you seem to have lost any advantage and
should scrap the local tables.
You will also find that there is not much discussion of macros here as vba
coding gives you far more flexibility in areas such as error-handling so if
a table was missing appropriate action could be taken rather than everything
grinding to a halt.

[cmcmillan]

I bothered doing it this way because when I was originally designing it
I was fairly new to Access. Since then I just hadn't given it a whole
lot of thought until this started happening. I see your point about
the linked tables, which makes more sense than what I'm currently
doing. Thanks for shedding some light on me.