Multi user options

S

STiruchi

I am planning to split the database for multi user purposes. The
questions I have is

1. Can I email the FE to all users and ask them to save on their
desktops (with the BE on one of the network drives).

2. If this is possible, then if I create the split from my PC, will
the path (or link to the BE on the network) be the same from other
users' PCs.

Thanks in advance for any help.

ST
 
A

Albert D. Kallal

STiruchi said:
I am planning to split the database for multi user purposes. The
questions I have is

1. Can I email the FE to all users and ask them to save on their
desktops (with the BE on one of the network drives).

If the path name remains the same, yes that will work. if not, then the
they'll have to teach them to use the linked table manager. Even better is
to provide your own re-link code that checks for the back end, and if not
then it can re-link. As a developer you will use the linked table manager
quite a bit during the the development process (especially if you're
developing and using a copy of the back and also. right before you deploy,
you'll need to remember to re-link to the production back end data)

2. If this is possible, then if I create the split from my PC, will
the path (or link to the BE on the network) be the same from other
users' PCs.

It's not really question will it be the same, it's a question is **are**
they going to do it that way.

The path name you have on your computer remains the same. If the computer in
question has access to the same shared folder on your network then yes, it
remains the same. (you don't have a problem).

You simply link your front end to the back end using UNC (the network path).
So link your front end to the back via network neighborhood. You wind up
with a path name that resolves to the network location.

If other users on your local office network have the same access to that
shareed folder where the back end resides, then the path name will remain
the same and no re-link need be done.

However if we talking about a differnt office network/computer, then you are
not assured that the path names remain the same at all. In this case you'll
have to teach your users to use the linked table manager, or do what most
developers have done and is develop some routines to check for the back end,
and if not found, then run your own custom re-link code.

That re-link code can look for the backend in some predefined location, or
simply pop up the file browse dialogue and let the user browse to the back
end.

You can use the code here to re-link.

http://www.mvps.org/access/tables/tbl0009.htm

You'll also find some code above web site that allows you to pop up the file
browse dialogue...

I talk about using network path names in the following split article of mine

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

The above also explains the process if you add a new table to your database,
how you go about adding this table to the front end...
 
M

Maurice

1. Yes you can do that
2. If you do the split from the networkdrive the link to the back end will
be correct for all the users. So first copy the db to the networkdrive and
split it there. Then send the frond end by mail and everything should work
just fine.

hth
 
P

pddxxx

1. Can I email the FE to all users and ask them to save on their
desktops (with the BE on one of the network drives).

Yes, but what happens when you update your front-end? Will you e-mail
it each time? What if they forget to save it?

There are some tools to help you automatically distribute an updated
front end. One I've written called Application Starter can be
downloaded from http://www.peterssoftware.com/aps.htm. Tony Toews has
his Auto FE Updater at http://www.granite.ab.ca/Access/autofe.htm
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top