Correct Sequence?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Can someone please enlighten me as to the correct sequence of events in
preparing to secure a db. Once I have my db completed and ready to be run
(over a network), should I split the db into FE and BE, then make the FE an
MDE. At this point do I then create my new workgroup information file and set
up the security I need.

Thanks for your continued support,

Ian.
 
I would
split
secure the frontend mdb
use the same workgroup file to secure the backend mdb
make the frontend into mde and distribute

any changes you need to make you do in the mdb. Once tested, you create a
mde and distribute.
 
Just to add a step to Joan's suggestion:
I would
Click to expand...

-- Make two backup copies of the file saved in different areas before beginning.
split
secure the frontend mdb
use the same workgroup file to secure the backend mdb
make the frontend into mde and distribute

any changes you need to make you do in the mdb. Once tested, you create a mde and distribute.
Click to expand...

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html
 
What's a backup?
Something you say quite frequently when something goes wrong.
Usually in the context of, "Why didn't I......"
Click to expand...

Actually, it's something us Texans say when someone is angry, "Don't get
your back up about that." <g>
 
Lynn said:
Actually, it's something us Texans say when someone is angry, "Don't get
your back up about that." <g>
Click to expand...

Same for us londoners!!! Although it does have other connotations too. ;-)

JJ.
 
Joan,

Finally worked my way through the maze that is Security, but not convinced
I've got it fully yet!! I followed your sequence and tried to make the MDE
file but Access won't do it. I get an error message saying Access is unable
to make the MDE file. I tried a couple of times but the same thing.

Sorry to hassle you but any suggestions?

Thanks,
Ian.
 
Open the MDB and hit Ctrl-G; Debug menu, Compile.

Fix any errors that it finds. Compile again, save.

In Access, Tools Database Utilities, Compact and Repair.

Now try to create the MDE.
 
Joan, thank very much, you're a hero.

I think what happened was that when I created a new db and imported in my
old objects so I was the owner the Reference to the DAO library was lost and
so Access couldn't recognise my DAO code. I've learnt a valuable lesson to
compile regularly to resolve problems.

Thanks again,
Ian.
 
It's something I have a tendency to forget as well. 2000 and 2002 don't set
a reference to DAO by default. When you create a new mdb, you have to set
that reference (and often uncheck the ADO reference)
 
Back
Top