Autoexec macro stored on backend - potential problem?

[Guest]

I'm having a problem with users opening the back end instead of the front end
of my database. As I am scared to death to implement Access security, I was
thinking of having a message box alert the user when he has opened the back
end. Can anyone foresee a problem with having an autoexec macro stored in
the back end of the database? (Sorry if this is a really dumb question...)

Thanks.

 

[Douglas J Steele]

I'm assuming you're talking about a macro that pops up a message box, then
shuts down the database after the user responds to the message box.

I've never had any problems with doing that.

 

[Joseph Meehan]

I'm assuming you're talking about a macro that pops up a message box,
then shuts down the database after the user responds to the message
box.

I've never had any problems with doing that.

Unless the user does not have a back door to get past it or forgets how
to get past it.

Not a dumb question, it is a good question.

I might suggest that Access security should not be all that scary, but
it does sound like you really don't need it, your approach should be fine
for the situation you are describing.

 

[Douglas J Steele]

Remember that we're talking the back-end database. No back door should be
required, since it only contains tables. You can easily copy the tables into
a new database if need be.

 

[Joseph Meehan]

Remember that we're talking the back-end database. No back door
should be required, since it only contains tables. You can easily
copy the tables into a new database if need be.

True. I had not thought of linking and copying.