|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Correct Sequence?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. -- Show quoteHide quoteJoan Wild Microsoft Access MVP Ian wrote: > 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. Just to add a step to Joan's suggestion:
>I would -- Make two backup copies of the file saved in different areas before beginning.Show quoteHide quote > 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. -- Show quoteHide quoteJeff Conrad Access Junkie - MVP http://home.bendbroadband.com/conradsystems/accessjunkie.html http://www.access.qbuilt.com/html/articles.html >> 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, Big thanks to Joan and Jeff. That all makes perfect sense.
Cheers, Ian. Show quoteHide quote "Jeff Conrad" wrote: > Just to add a step to Joan's suggestion: > > >I would > > -- 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. > > -- > Jeff Conrad > Access Junkie - MVP > http://home.bendbroadband.com/conradsystems/accessjunkie.html > http://www.access.qbuilt.com/html/articles.html > > >> 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, > > > What's a backup?
<g> -- Show quoteHide quoteJoan Wild Microsoft Access MVP Jeff Conrad wrote: > Just to add a step to Joan's suggestion: > >> I would > > -- 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. > > -- > Jeff Conrad > Access Junkie - MVP > http://home.bendbroadband.com/conradsystems/accessjunkie.html > http://www.access.qbuilt.com/html/articles.html > >>> 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, "Joan Wild" wrote in message:
news:%23vWlnz3mGHA.1208@TK2MSFTNGP03.phx.gbl... Something you say quite frequently when something goes wrong.> What's a backup? Usually in the context of, "Why didn't I......" <g> -- Jeff Conrad Access Junkie - MVP http://home.bendbroadband.com/conradsystems/accessjunkie.html http://www.access.qbuilt.com/html/articles.html >> What's a backup? Actually, it's something us Texans say when someone is angry, "Don't get > > Something you say quite frequently when something goes wrong. > Usually in the context of, "Why didn't I......" your back up about that." <g> -- Lynn Trapp Lynn Trapp wrote:
>>> What's a backup? Same for us londoners!!! Although it does have other connotations too. ;-)>> Something you say quite frequently when something goes wrong. >> Usually in the context of, "Why didn't I......" > > Actually, it's something us Texans say when someone is angry, "Don't get > your back up about that." <g> > 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. Show quoteHide quote "Joan Wild" wrote: > 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. > > > -- > Joan Wild > Microsoft Access MVP > > Ian wrote: > > 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. > > > 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. -- Show quoteHide quoteJoan Wild Microsoft Access MVP Ian wrote: > 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. > > "Joan Wild" wrote: > >> 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. >> >> >> -- >> Joan Wild >> Microsoft Access MVP >> >> Ian wrote: >>> 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. 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. Show quoteHide quote "Joan Wild" wrote: > 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 Wild > Microsoft Access MVP > > Ian wrote: > > 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. > > > > "Joan Wild" wrote: > > > >> 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. > >> > >> > >> -- > >> Joan Wild > >> Microsoft Access MVP > >> > >> Ian wrote: > >>> 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. > > > 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) -- Show quoteHide quoteJoan Wild Microsoft Access MVP Ian wrote: > 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. > > > "Joan Wild" wrote: > >> 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 Wild >> Microsoft Access MVP >> >> Ian wrote: >>> 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. >>> >>> "Joan Wild" wrote: >>> >>>> 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. >>>> >>>> >>>> -- >>>> Joan Wild >>>> Microsoft Access MVP >>>> >>>> Ian wrote: >>>>> 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. 
Other interesting topics
self-signing certificate
Windows UserID and Access Problem with References Import to bypass security Read only for staff RE: ade to adp - utility available to help protect source code Lost mdw files Clear Password through VBA Open Access from an Access program that is currently running Security issues. |
|||||||||||||||||||||||
