Front end/Back end

[Guest]

I am not very knowledgeable in Access, aside from being able to create tables
and forms, no code. I use access on a shared drive, but I am the only one
who makes changes to it, all other users input data on forms only. Sometimes
I can not open it when someone else is in it, and I get a message that says
"the database has been placed in a state by user 'some name' on machine 'some
computer ID' that prevents it from being opened or locked. I read some posts
regarding front end/back end files. It sounds like this is what I need. Can
this be done by a novice, or will it take someone with more skill? If it can
be done by a novice, where can I go to find out how to do it? Thank you.

Greg Snidow

 

[Guest]

it's extremely easy, but you have to take into account whether or not you've
implemented security.

to split the database do the following
Make a back up copy first.
Then make another copy that will be the back end.
On the back end database, delete everything except tables.
On the original delete all the tables.
Then go to file|Get external data| and select link tables.
Point to the "Backend database" and select all the tables.

That's pretty much all you have to do. Give everyone a copy of the front end.
Make sure the path you use is \\computername\sharename\ schema rather than
some drive letter pointed to the network, because the scheme above will be
the same for all computers. A drive letter might not be.

If you have security implemented there are various posts you can search for
that have a link to the steps you would take but basically you implement
security on both the front end and the back end.

You only concern after that is that when you make changes, you make sure
everyone gets a copy of the new front end. This can be done through various
update programs, or even a batch file.

 

[Guest]

Just make a backup copy of your DB as is before you start, then do this.

Make two copies of the DB. Remove everything except the tables from one and
only the tables from the other (this will involve removing the table
relationships as well if there are any). The one with the tables becomes your
backend; the one without becomes your front end.

Now, in your front end, go to File -> Get External Data -> Link Tables.
Browse for & select your backend file. Click Select All to select all its
tables, and when it is done, your front end should work as it did before. It
will be completely transparent to the user and allows you to work on your
developer's copy of the program file without kicking everyone out of the
application, except for the two minutes when you replace the live front end
with your newly-updated one.

Keep in mind that if you try to make a change to the front end while someone
else is in it (or at least in the form you are redesigning), you will not be
able to save your changes. Just make a copy of the file, make your changes,
and then copy your new front end over the old front end.

 

[Guest]

Thank you to both of you, you make it sound so easy. I think I may be able
to figure it out based on your input.

 

[Mike Revis]

Hi,

Please excuse my butting in here but I'm curious.

This is the first time I have heard of making a front/back end in this
manner.

I have made front/back end using the database splitter wizard.

Is there any advantage to making a front/back end using the method you
suggest as opposed to the splitter.

Mike

 

[Guest]

I do not know much about access, but when I made a front/back end like they
told me to my problems with multiple users stopped. It seems to me that
everyone still has access to the tables, which I do not like, but maybe there
is a way to stop that.
Greg Snidow

 

[Jack MacDonald]

I've never used the wizard-- I always split manually. Have heard that
the wizard does not properly transfer user-level security permissions,
whereas the manual method clearly does transfer them properly.

Splitting manually has the benefit of *you* understanding what is
behind the scenes. Knowledge is power...

Hi,

Please excuse my butting in here but I'm curious.

This is the first time I have heard of making a front/back end in this
manner.

I have made front/back end using the database splitter wizard.

Is there any advantage to making a front/back end using the method you
suggest as opposed to the splitter.

Mike

**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

 

[Guest]

The wizard does not handle user level security. If you have implemented
security, do not use the wizard to split the database. Clearly when you copy
the database both databases still have security implemented. When you remove
tables from the front-end or all other objects from the back end, the
security for the remaining objects remains in-tact.

 

[Mike Revis]

Thank you,
That satisfies my curiosity.
Since I have never dabbled in security issues I guess I have never noticed.

Mike