Workgroup File Replacement

[Brigham Siton]

Is there any replacement for this WRKADM?

Can I create a startup form in a FrontEnd MDE file that compares Username &
Password on a backend userlist table?

And if the username and password is not there or does not match, that they
will not allow
access?

They can not edit anything anyway the MDE files so I could care less on the
User-Level Security.

Can someone advise me on pros & cons and direct me to the right direction?
Any sample coding perhaps you can share on how to do this?

Thank you very much.

 

[TC]

If you do not use Access user-level security, what is to stop someone from
opening the back-end database directly, & reading the usernames/passwords
out of your table?

TC

 

[Brigham Siton]

That is true indeed. It is possible for users to go to the table and look
for username and passwords and open that file.

However, though its not the best thing to do, it will not be easy to open
the mde file and look where is the linked table.

The main reason that I am thinking on doing this is that we have Access 97
on about 15 machines.

We recently upgraded and leased 15 new machines with XP Pro and Office XP
pro.

I was able to join them to our access.mdw file. However, even they are
joined already, they are not being prompted for a username & password. I
tried changing the link to show the /wrk on the path to no avail.

I do not know what else to do.

Any suggestions?

 

[Rick Brandt]

That is true indeed. It is possible for users to go to the table and look
for username and passwords and open that file.

However, though its not the best thing to do, it will not be easy to open
the mde file and look where is the linked table.

The main reason that I am thinking on doing this is that we have Access 97
on about 15 machines.

We recently upgraded and leased 15 new machines with XP Pro and Office XP
pro.

I was able to join them to our access.mdw file. However, even they are
joined already, they are not being prompted for a username & password. I
tried changing the link to show the /wrk on the path to no avail.

I do not know what else to do.

Your link is not correctly built and you didn't correctly join them to the
mdw. If they were using an mdw with a password on the Admin user then they
_will_ get prompted. You can run the following command to see what mdw
file the user is operating under...

SysCmd(acSysCmdGetWorkgroupFile)

Security "light" has its place in many circumstances, but if you have
already gone to the trouble of setting up Access User-Level security, you
should go ahead and get that working properly rather than going through a
redundant effort.

BTW, if they are not getting prompted and are still getting in, then you
didn't apply security properly. Anyone using the wrong mdw file should be
denied access to the file completely.

 

[Brigham Siton]

Thank you very much for the input.

Then I will invest my time continuing what I was doing.

I will start from scratch again.

Thanks for the input guys.