Read Only

[Stockwell43]

Hello,

I have a question that should be fairly easy. I have a database that when
opened will pop up the mani menu. It has two cbo's one form the main form and
the other to pull reports. The database is secure and guts are all password
protected even against the Shift Bypass. However, if someone import the
database into an empty shell, everything will be exposed. Is the a way to
prevent someone from importing the database? Making it like read only or
something?

Thanks!!

 

[Jeff Boyce]

Not sure if this would do it, but have you tried "Create .MDE"?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Stockwell43]

No Sir. Is that splitting the database? If so, I hate to split it just to
keep it protected. If not, how do I create a .MDE?

Thanks Jeff!

 

[Jeff Boyce]

NOTE: making an MDE means you will NOT be able to "get into" the MDE to
make changes. Make a backup copy of your MDB file (you're doing that
anyway, right?!), then see next...

Depending on which version of Access you are using, try "Tools" | "Database
utilities" | "Make .mde".

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Stockwell43]

Hi Jeff,

Yes, I always make a copy before I make any changes to the original.

This works great. However, I was looking for something along this line but
only being able to edit or update, make changes and so forth by the
administrator. Is this possible without it getting too involved?

Thanks!!!

 

[Jeff Boyce]

Not that I'm aware of, unless you are willing to take on the semi-
(?psuedo-) security Access (?earlier versions) offers.

A common approach is that you, as Admin, would keep the MDB copy, so you
could make changes and re-make an MDE version, which you'd then deploy.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Stockwell43]

Thanks Jeff, I understand.

Well, I guess I can go that route because I can import the tables and
queries from the MDE so if I make any changes to the MDB, I can import the
table of the MDE so the records and information is current is that the
correct approach?

Thanks!!!

 

[Jeff Boyce]

I don't believe you can "import" from your MDE. That's why I mentioned
saving a copy of the MDB ... that's what you'd be altering.

Of course, if you've "split" your application to a front-end (which you are
deploying as an MDE, so users and you cannot change it) and a back-end (one
only, stores the data), you'd still be able to see the data whenever you
needed to. No need to "import tables".

Regards

Jeff Boyce
Microsoft Office/Access MVP