Re: Multi users Logon Security questions

reeve13 wrote:
>
> The next thing I need to do is split the database so others can work
> in it. Before doing this, I have a few questions:
>
> (Your instruction) Step 1 - Make a copy of the database - this will be
> the backend.
>
> Question: Am I making a copy of the shortcut database located on my
> desktop that was created earlier from the "security step by step
> instructions"?

No. You can right-click that shortcut and look at the target. That will
show you the location of the mdb. Click Cancel. Now open Windows Explorer
and navigate to the mdb - copy the mdb. I'd give the copy some name to
easily distinguish it from the frontend.

> (Your instruction) Step 2 - Open the backend and delete all objects
> except the tables.

You can use your desktop shortcut (which will open your frontend). Then use
Ctrl-O and open the backend mdb. Then delete all objects, except the
tables.

> Question: I created a switchboard in my original database, and
> deleting all objects except for the ones in the table, am I going to
> get error messages when I try to open any forms and Reports in the
> backend database?

You might. I would make an exception to the switchboard...see below.

> (Your instruction) Step 3 - Open your original database and delete the
> tables/relationships.
>
> Question: I assume the original database is the one I am unable to
> open. How do I get around this?

No it isn't. You can use the desktop shortcut to reopen the frontend (or if
Access is still open, use Ctrl-O and open the frontend). The frontend being
the secure single mdb, not your original unsecured mdb. Now delete the
tables/relationships *except* for the Switchboard table (I think it's called
Switchboard Items). Leave that in the frontend. Next I'd put the backend
on the server in a folder that all users have modify permissions on. Then
you can use File, Get External Data, Link Tables....and link to the backend
in its new location - If you navigate to the backend using network
neighborhood, you'll get the UNC pathname which is preferred over using a
mapped drive letter. When you link to the backend, be certain that you
don't include the Switchboard Items table (since that will exist in the FE).
Finally you can open the backend and delete the Switchboard Items table.

--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • Re: Split Database Security Problem
    ... Both frontend and backend ... > permissions, but as in all good stories there is a catch. ... The newAdmin for the 'object database' has the ...
    (comp.databases.ms-access)
  • RE: Form on front end loading slowly
    ... I gather the user has a frontend that uses a backend database on a server ... > have a database backend with a table that lists employees, ...
    (microsoft.public.access.formscoding)
  • Re: Split Database Security Problem
    ... Both frontend and backend ... > permissions, but as in all good stories there is a catch. ... The newAdmin for the 'object database' has the ...
    (comp.databases.ms-access)
  • Re: Comiling problems
    ... (No private e-mails, please) ... > networked PCs each with a 'frontend' mdb that uses linked ... > tables from the 'backend'. ... > tried creating a new mdb and importing the tables from the ...
    (microsoft.public.access.modulesdaovba)
  • Split Database Security Problem
    ... I have managed to secure a split database. ... Both frontend and backend ... permissions, but as in all good stories there is a catch. ...
    (comp.databases.ms-access)