Please help with 3033 error

[Farmer]

Hi, (I have also posted that question in
microsoft.public.access.security please respond there)
I have tried to find an answer to my question but I am finding it
impossible. This is the problem: I have created a database with a
front-end and two back -ends the reason beeing that i want the first to

be public (as in its file premissions) and the other limited to a
ceratin group. I have followed the ms security faq on securing a db and

created an .mdw. I run the db through a batch file that checks for
newer files on the network share and then runs the db through a
shortcut the points to an .mde (which is a copy of the original .mde
file in the share)
with the switch /wrkgrp that points to a local copy of the .mdw. I have

changed the users file access permissions to :C for the back end. I
have even made him a member of adm (which my new admin group), and all
the other groups for that matter. It is still impossible for them to
open the bl***y database with an 3033 error (dont have enough
permissions for the object). I am close to commiting computicide.
Please, for the love of <your worship object here> give me a hand!! I
am desparate
Thanks

[Mark Reed]

Unlike most that post here, I am no expert but I believe you have made a few
mistakes. I do not understand why you would need two backends? If there are
a group of tables that require full access to everyone, permissions can be
set to reflect this as they also can for tables that require selected
access.

I get the impression that each PC running the database has it's own copy of
your workgroup (mdw) file somewhere on the C: drive? Whenever I have
distributed a database over a network, I have only one copy of the mdw
(besides a backup) stored on the network. The frontend shortcut distributed
with the frontend then has a command line argument pointing to this mdw
file. If you just have the one mdw, it will be a lot easier keeping track
over which user/group has access to what!!!

Regards,

Mark

"Farmer" <kn******@gmail.com> wrote in message
news:11**********************@j33g2000cwa.googlegr oups.com...

Hi, (I have also posted that question in
microsoft.public.access.security please respond there)
I have tried to find an answer to my question but I am finding it
impossible. This is the problem: I have created a database with a
front-end and two back -ends the reason beeing that i want the first to

be public (as in its file premissions) and the other limited to a
ceratin group. I have followed the ms security faq on securing a db and

created an .mdw. I run the db through a batch file that checks for
newer files on the network share and then runs the db through a
shortcut the points to an .mde (which is a copy of the original .mde
file in the share)
with the switch /wrkgrp that points to a local copy of the .mdw. I have

changed the users file access permissions to :C for the back end. I
have even made him a member of adm (which my new admin group), and all
the other groups for that matter. It is still impossible for them to
open the bl***y database with an 3033 error (dont have enough
permissions for the object). I am close to commiting computicide.
Please, for the love of <your worship object here> give me a hand!! I
am desparate
Thanks

[Farmer]

Thank you for your reply Mark,
I am no expert either, but I think that my rationale of having two back
ends makes sense because I you might be able eventually to read a file
for which you have a copy (I am speculating) so why not be on the safe
side and exclude people from accessing it which is easy enough (I use
xcacls.exe). Any way my mistake was very silly and it was that I had
overlooked the object database and had not set any permissions for it (
I had assumed that since you have permissions to see the file you
should be able to open it). Anyway I corrected it and it works fine.
You are right the Pc running the database has it own copy somwhere in
the C: drive and I have set the startup batch to copy the mdw every
time it runs. I did this because i was not sure whether you can access
the mdw simultaneusly. So you are saying that this is possible to have
concurrent access to the mdw?

[Keith Wilby]

"Farmer" <kn******@gmail.com> wrote in message
news:11**********************@y43g2000cwc.googlegr oups.com...

You are right the Pc running the database has it own copy somwhere in
the C: drive and I have set the startup batch to copy the mdw every
time it runs. I did this because i was not sure whether you can access
the mdw simultaneusly. So you are saying that this is possible to have
concurrent access to the mdw?

Yes, the "classic" arrangement is to have it in the same place as your BE on
the server.

Keith.
www.keithwilby.com

[Mark Reed]

Yes you can have many concurrent users of a singular mdw. As for the upper
limit of this, I do not know but 15-20 users use one of my apps all sharing
1 mdw with no issues.

Mark

"Farmer" <kn******@gmail.com> wrote in message
news:11**********************@y43g2000cwc.googlegr oups.com...

Thank you for your reply Mark,
I am no expert either, but I think that my rationale of having two back
ends makes sense because I you might be able eventually to read a file
for which you have a copy (I am speculating) so why not be on the safe
side and exclude people from accessing it which is easy enough (I use
xcacls.exe). Any way my mistake was very silly and it was that I had
overlooked the object database and had not set any permissions for it (
I had assumed that since you have permissions to see the file you
should be able to open it). Anyway I corrected it and it works fine.
You are right the Pc running the database has it own copy somwhere in
the C: drive and I have set the startup batch to copy the mdw every
time it runs. I did this because i was not sure whether you can access
the mdw simultaneusly. So you are saying that this is possible to have
concurrent access to the mdw?

[Farmer]

Well I think I will follow the classic method then, thanks very much
guys

[David W. Fenton]

"Farmer" <kn******@gmail.com> wrote in
news:11**********************@y43g2000cwc.googlegr oups.com:

You are right the Pc running the database has it own copy somwhere
in the C: drive and I have set the startup batch to copy the mdw
every time it runs. I did this because i was not sure whether you
can access the mdw simultaneusly. So you are saying that this is
possible to have concurrent access to the mdw?

And MDW is just a special kind of MDB file with some properties that
regular MDBs do not have.

Make a copy of your SYSTEM.MDW and try opening it in Access. You'll
find that you can see all sorts of interesting things.

This also means that MDW files can be compacted, and may benefit
from it occasionally.

All that said, I sometimes distribute an individual MDW for
applications where performance considerations are crucial, as
contention for the MDW file can cause performance slowdowns. I make
copying a new MDW part of the front-end update process.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Farmer]

So could i just add a user by adding him to msysacount and msysgroups ?

[David W. Fenton]

"Farmer" <kn******@gmail.com> wrote in
news:11**********************@v46g2000cwv.googlegr oups.com:

So could i just add a user by adding him to msysacount and
msysgroups ?

Well, not directly -- you can't edit those tables directly. You do
it by using the security UI in Access, or through the DAO interfaces
for creating users/groups.

I didn't mean to imply that since an MDW is just an MDB with some
special properties that it should be edited like an MDB. I only
wanted to show that there is nothing magic about an MDW file.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/