Strange problem with secured database--Urgent HELP Needed

xunitinmullik

Hello ppl:
I am facing a problem that I ahve never experienced before with the
secured database. I created an MS Access 2000 application (.mdb) using
MS Access 2002 and secured it using exactly the procedure described in
the Access Security FAQ and as I have been doing since the time I
have started using Access.
So let the access application be xxx.mdb. After completing the whole
development for xxx.mdb, i secured it using the procedure defined in
the FAQ and created the Workgroup information file for it, say
xxx_WIF.mdw. I tested it for my satisfaction and everything was
working exactly the way it is supposed to.
Now the problem I am facing is, that when the project went into QA
phase, the QA team observed that on the machines that the application
was installed for testing, the users were able to open and use the
application without using its defined workgroup information file
(xxx_WIF.mdw) and the default WIF of windows worked for them to open
the database.
Then i again tested on my beta machine and 4 other machines and quite
surprisingly it works fine on 3 machines i.e. I am not able to acess
the application without using xxx_WIF.mdw but on other two machines,
the user is able to open it using the default windows WIF
(system.mdw). (All machines use MS Access 2002 with SP3 installed)
I tried many methods to observe the reason for this behavouri but was
unsuccesfull and now have to turn to the community for SOS. Any inputs
from the community will be highly appreciated and is needed urgently
as the application is scheduled to be deployed into a couple of days.
Thanks,
Nitin

Peace :)

Nov 13 '05 #1

Rick Brandt

"xunitinmullik" <ni**********@yahoo.com> wrote in message
news:da**************************@posting.google.c om...

Hello ppl:
I am facing a problem that I ahve never experienced before with the
secured database. I created an MS Access 2000 application (.mdb) using
MS Access 2002 and secured it using exactly the procedure described in
the Access Security FAQ and as I have been doing since the time I
have started using Access. [SNIP]
Now the problem I am facing is, that when the project went into QA
phase, the QA team observed that on the machines that the application
was installed for testing, the users were able to open and use the
application without using its defined workgroup information file
(xxx_WIF.mdw) and the default WIF of windows worked for them to open
the database. [SNIP]

When you go into Tools - Security who does it show is the owner of the
database?

There is simply no getting around the fact that when you open an mdb using
a workgroup file that does not ask you to log in, then you are then logged
in as "Admin" who is a member of "Users". A properly secured file cannot
be opened with such an account. It is a mystery why only "some" machines
are allowed to open it without logging in, but I have to believe that you
missed a step in setting up security.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Nov 13 '05 #2

xunitinmullik

"Rick Brandt" <ri*********@hotmail.com> wrote in message news:<2n************@uni-berlin.de>...

When you go into Tools - Security who does it show is the owner of the
database?

There is simply no getting around the fact that when you open an mdb using
a workgroup file that does not ask you to log in, then you are then logged
in as "Admin" who is a member of "Users". A properly secured file cannot
be opened with such an account. It is a mystery why only "some" machines
are allowed to open it without logging in, but I have to believe that you
missed a step in setting up security.

Thanks for your inputs and time Rick.
The owner of all the objects is a user who is the member of Admins
group and i created to administer the project. Default "Admin" also
has been stripped of all the rights with no permissions assigned to
"Users' group too. But then anything being wrong with that is a
secondary issue. The main issue that I am facing is that the
application is getting opened by a WIF that was not used to secure it.
Any further inputs to rectify the problem will be appreciated.
Thanks in advance.

Nitin

Peace

Nov 13 '05 #3

Rick Brandt

"xunitinmullik" <ni**********@yahoo.com> wrote in message
news:da**************************@posting.google.c om...

"Rick Brandt" <ri*********@hotmail.com> wrote in message

news:<2n************@uni-berlin.de>...

When you go into Tools - Security who does it show is the owner of the
database?

There is simply no getting around the fact that when you open an mdb using
a workgroup file that does not ask you to log in, then you are then logged
in as "Admin" who is a member of "Users". A properly secured file cannot
be opened with such an account. It is a mystery why only "some" machines
are allowed to open it without logging in, but I have to believe that you
missed a step in setting up security.

Thanks for your inputs and time Rick.
The owner of all the objects is a user who is the member of Admins
group and i created to administer the project. [snip]

Just to be completely clear, when you say "all objects" you mean the database
object as well, correct? This is an oft missed step when setting up security.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Nov 13 '05 #4

xunitinmullik

"Rick Brandt" <ri*********@hotmail.com> wrote in message news:<2n************@uni-berlin.de>...

"xunitinmullik" <ni**********@yahoo.com> wrote in message
news:da**************************@posting.google.c om...

"Rick Brandt" <ri*********@hotmail.com> wrote in message

news:<2n************@uni-berlin.de>...

When you go into Tools - Security who does it show is the owner of the
database?

There is simply no getting around the fact that when you open an mdb using
a workgroup file that does not ask you to log in, then you are then logged
in as "Admin" who is a member of "Users". A properly secured file cannot
be opened with such an account. It is a mystery why only "some" machines
are allowed to open it without logging in, but I have to believe that you
missed a step in setting up security.

Thanks for your inputs and time Rick.
The owner of all the objects is a user who is the member of Admins
group and i created to administer the project. [snip]

Just to be completely clear, when you say "all objects" you mean the database
object as well, correct? This is an oft missed step when setting up security.

Yes Rick, the database as well. This is the most disturbing point.
Everything seems to be in place, though i am sure that there is
something wrong somewhere that is causing the behaviour. Any other
things that i should consider? Guess, will have to implement it again
from start on the backup file if the issue doesn't resolves soon.

Nov 13 '05 #5