Shared Database

[KenE]

Hi, I am a intermediate user of Access and having great difficulty with my
first split database, let me explain my problem.

I created a database that uses files that I've linked to and split the
database to be/fe, since I would have many people using the database for
queries, reports etc I didn't want them to have access to the many tables.
When I split the database and put the back end in our shared folder, the
database wouldn't work as it could not link to the databases I've linked to?

Example; The two databases I need are out on a network, I linked these two
databases to my hard drive with seperate drive letters (s;y, all my queries
and such are derived from these tables. Well once I completed the database I
created and went to give a presentation, it would only work on my computer.

Here's my dilema, how can I create a databse that will allow me to use
tables from another source, and have other able to use the database also?

Will everyone in my area (15) need to also map to these two databases?

Please forgive me If I am less than clear, I hope someone can understand
this. I've put a lot of time and energy into this database, and it seems for
nothing

Thanks KenE

 

[Albert D. Kallal]

You should as a rule avoid using drive letters, since then all users will
have to have that drive mapping.

You better to use UNC.

I explain the ins and outs here:

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

 

[Tony Toews [MVP]]

You should as a rule avoid using drive letters, since then all users will
have to have that drive mapping.

Well, I disagree that that concept is a rule. Instead it's a
guideline.

You better to use UNC.

The other side of that is what if the name of the server or the name
of the shared folders change?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[KenE]

Albert, thanks for the information. If I understand this correctly, if I put
my BE on a server which we are all connected to, the users will be able to
use the FE?

Of course, I have to find out how to save a file to a server.

 

[Albert D. Kallal]

Well, I disagree that that concept is a rule. Instead it's a
guideline.

yes...a "guide line" is *much better* term here..

a few people have well pointed out that adopting drive mapping can actually
solve a LOT of problems. I believe it was Tom Wickerath, or Douglas Steele
made a terrific case that their company could not manage their large
deployments without the use of mapped drives (the added benefit is that you
can *change* that drive on the server side).

so, good idea to use UNC, but I seen some good cases made for those mapped
drives.....

 

[Albert D. Kallal]

Albert, thanks for the information. If I understand this correctly, if I
put
my BE on a server which we are all connected to, the users will be able to
use the FE?

yes. The idea here is if you link to the fe to the be via UNC path names.
you then distribute this FE to each machine. When they launch the
application, it will connect to the back end.....

Often, we will write and provide some code to "test" for the link at
startup, and allow the user to browse to the back end, but this will would a
fall back position to having the fe already linked before you give/place it
on the users machine...

 

[KenE]

Albert, one more question please. If the data in my be is from a linked data
source which I have access to, do each of the users need access to this data
also?

My data is from a different area in my company, and I have been granted
access to the data for which I created my database. If they are linked tables
do all users require the same security rights? Is there any way around this?
The don't actually see the tables, just queries, forms and reports I've
created.

Thanks.

 

[KenE]

Albert, one more question please. If the data in my be is from a linked data
source which I have access to, do each of the users need access to this data
also?

My data is from a different area in my company, and I have been granted
access to the data for which I created my database. If they are linked tables
do all users require the same security rights? Is there any way around this?
The don't actually see the tables, just queries, forms and reports I've
created.

Thanks.

 

[Albert D. Kallal]

Gee, my newsreader missed this....


Yes, all users need access to that directory where the back end resides.

This is not different then a user wanting to open a power-point file...they
have to be able to see the file....