Is there an easy way to log out as one user and then log in as a different
user without closing an application?

We have a split FE/BE database I have taken over as the developer, one aspect
was to introduce user level security.
We run access 2002. However the database was of access 2000 format, so first
it was converted to 2002 format before being secured. Then I found you could

I may have locked myself out of my database.  I'm hoping someone has work
around.
I turned off special keys and I set allowbypasskey to off.  Its been a
while, but I believe I also set the DDL option to true, meaning you cannot

I have a replicated database (back end with tables only) which was created
with no security enabled so "admin" own all the objects in the database. I
now come to learn that allowing "admin" to own everything is not desirable
if I want to be able to secure my data.

Is there a way to set up a new user and then force them to create their own
password the first time they log on?

I have read several previous postings and tried the advice without
success.
Shared Access 2002 database written by someone who left the company,
but states she did not add security or create a new workgroup.  Access

I have a user that trying to creat a simple report with access 2003.the
secruity on the database is set to the default setting. the user is member of
power users group. he go thru the wizard and then when click finish it fails.
if we log on as the local administrator of course it ...

I've created a new security (mdw) file and joined the workgroup. I created
some users and groups, put myself in admins and took admin out. I put a
minimal password on the user "admin".
I created a new database whiled logged in as myself so that I would own the

I will have two unique databases on my network. One will have a group .MDW
file for user rights and the other DB is not secured.
I am trying to specifing the "Application.SetDefaultWorkgroupFile" with VB
code on startup of the secured DB to ensure the user is properly joined to

Hello everybody.I am trying to find if there is a possibility to hide the
connection between the fe and be so noone could know where the be exists.I
don't want simple users that play with the database to copy and paste the
shared file that contains the data and take it at home..

Whenever I start Access 97 the logon window appears even if I don't specify a
workgroup file in the command line of the shortcut.  How could I suppress the
logon screen?

Can anybody help me how to create a system.mdw file by code DAO ??
Thank you !
Javier

I have set a password on the backend of my database, now when I try to open a
linked table or a form in the front end of the database it gives me a "Not a
valid Password" message box.  Is there a way to keep the password on the
backend of the database but still be able to access ...

I have a FE/BE app, both parts are secured. I'd like to use a routine in the
FE to update the structure of the BE (adding tables / fields etc).
This works great with the non-secured BE, but I am struggling to determine
if this is possible with a secured BE. I use a table of tables ...

does anyone know if it is possible to convert an access database (.mdb) to a
stand alone (.exe) format. Or if someone has designed any software to do this
and maintain all the access functions?
also; on a similar note; how do you create an install screen for a file, that