User or group permissions in database

[Peter]

Is there any way to have the User of the database be defaulted to
the login of the XP system when they open the database?

I am trying to avoid having the user log onto the computer and then
have to login in to the database when they open it.

 

[Rick Brandt]

Is there any way to have the User of the database be defaulted to
the login of the XP system when they open the database?

I am trying to avoid having the user log onto the computer and then
have to login in to the database when they open it.

No.

 

[Jeff Conrad]

Humm...I suppose you could create a non-secured database
and have a shortcut icon to that on the user's desktop.
The non-secured one would run some code via a Autoexec
macro that would capture the network login via an API
and then open up the secured database (by passing in all
the correct parameters) with the supplied User Name.
Once the secured file is open the unsecured one would close.
You would of course have to hard code in the user's password
or use no password.

In theory this should work, but it sort of defeats the purpose
of securing the database in the first place don't you think?
Let alone managing new users, changed passwords, changed
Network Login IDs, etc.

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html


in message:

 

[Rick Brandt]

Humm...I suppose you could create a non-secured database
and have a shortcut icon to that on the user's desktop.
The non-secured one would run some code via a Autoexec
macro that would capture the network login via an API
and then open up the secured database (by passing in all
the correct parameters) with the supplied User Name.
Once the secured file is open the unsecured one would close.
You would of course have to hard code in the user's password
or use no password.

In theory this should work, but it sort of defeats the purpose
of securing the database in the first place don't you think?
Let alone managing new users, changed passwords, changed
Network Login IDs, etc.

That would only provide the user name though and not the password. Since the
user name will automatically default to the last one entered you really get no
benefit from it.

 

[Jeff Conrad]

in message:

Hi Rick,

That would only provide the user name though and not the password. Since the
user name will automatically default to the last one entered you really get no
benefit from it.

Yes, I agree, which is why I said this:

Meaning the password would have to be included in the code
that opens up the secured database.