Re: secured db, yet insecure with alternate worgroup file..
- From: "TC" <aatcbbtccctc@xxxxxxxxx>
- Date: 10 Dec 2005 20:33:11 -0800
A quick check of your original post suggests that you may have omitted
a critical step: namely, changing the /ownership/ of the objects in the
database.
In order to get this right, it is really necessary to follow a written
list of explicit instructions - adding & omitting nothing. It's too
hard to get it right, in any other way.
I suggest you start again, and follow the Access Security FAQ (often
referenced in this newsgroup), or, the instructions on any of the
regular posters' excellent websites!
HTH,
TC
.
- References:
- Re: secured db, yet insecure with alternate worgroup file..
- From: Rick Brandt
- Re: secured db, yet insecure with alternate worgroup file..
- Prev by Date: Re: Loading access using a generic acct
- Next by Date: Re: Force Maximize on Access Startup using .VBS by TC
- Previous by thread: Re: secured db, yet insecure with alternate worgroup file..
- Next by thread: Re: secured db, yet insecure with alternate worgroup file..
- Index(es):
Relevant Pages
|