Backend/Frontend Issue

[Guest]

I have succesfully 'split' my database into frontend & backend. However, I
have a couple of questions.

Both the back and front exist on our server, and everyone is linking to the
frontend database. Is this ok and is this what is meant by everyone having
their own frontend copy?

Also, there is now no security on the backend database, you can just open it
up without loggin in. I created a password but when you go to open the
frontend it says password not valid.

I'm a bit confused with all this. Is there any detailed documentation
anywhere that I could refer to?

Many thanks

 

[Albert D.Kallal]

Both the back and front exist on our server, and everyone is linking to
the
frontend database. Is this ok and is this what is meant by everyone having
their own frontend copy?

No, the above is incorrect. The idea and concept here is install the
application on each computer.

Also, there is now no security on the backend database, you can just open
it
up without loggin in. I created a password but when you go to open the
frontend it says password not valid.

Well, if you had stared out with a copy of the front end on each pc..then
very likely the users would never even know about the back end part.

I just put a macro in the back end..and when run the users are kicked out.

So, I make a macro called AutoExec. In the macro, I put the following code:

Action Parms
Msgbox message:You do not have permissions to run this file
Beep: Yes
Type: Critical
Title: Can not run

Quit: Options:Exit

As an alterative, you an make a nice little form in the back end, and set
the startup options to run that form that displays a message, and then when
they click ok...you do a application.quit.

And, to disable the "shift key", simply grab my shift key utility here to
turn off the shift key by-pass

http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

I'm a bit confused with all this. Is there any detailed documentation

anywhere that I could refer to?

Sure, read my article on this subject...after you are done..all should be
clear...
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Allen Browne]

The ideal is to install a copy of the front end onto everyone's local hard
disk.

If that is not feasible, you can get away with putting a different copy of
the front end into each user's individual workspace on the server, so they
everyone is opening a separate mdb file. This is a little slower, and caues
considerably more network traffic, but is safe.

What you must not do is give everyone a link to the *same* front end file on
the network.

Security is a large topic. You may be aware that Access has security
features through an MDW file. If your goal is to keep people away from the
data itself, that will be the way to go. If you just want to ensure that
users are modifying your forms or changing your code, create an MDE and give
that to each user as their front end.