Hi Neil,
In addition to the answer provided by Immanuel Sibero, I would add that you
really do not want to use mapped drive letters (ie. Z:\). You will be much
better off using the UNC (Uniform Naming Convention) equivalent to a mapped
drive. You can usually learn the UNC equivalent by using the My Network
Places desktop shortcut. One must know the UNC equivalent the first time they
go to map a network drive.
The IT Dept are now going back on their word.
That kind of sucks. I think you need to get your management involved, and
have them talk to the management of the IT Department.
I have just been told today that the IT Dept at my workplace does not
support MS Access (no reason given).
This sounds like a turf war to me. It is not uncommon for IT types to have
feelings like this. They tend to perceive Access as a threat to their job
security. Instead, they should be welcoming it, because it is likely to bring
additional work to them. However, too many times, people will drop really
poorly designed databases into the laps of IT departments and tell them to
"make it work". I have seen this attitude at The Boeing Company many times
before. In your case, you have a properly designed relational database, so
this should not be a valid argument. You should read the following article:
Why IT Departments Hate Access
http://www.fmsinc.com/tpapers/genaccess/DBOD.asp#hateaccess
It permits its use, but doesn't support it technically.
The only things that they really need to support are:
1.) Providing a shared folder that all qualified users have RWCD privileges
to. The UNC path for this folder should be as short as possible in overall
length. In addition, you don't want any part of the folder specification to
exceed the 8 character limit, since that is known to slow certain operations
down.
and
2.) Assistance with installing the latest service packs for the operating
system, Office, and the JET database engine on any PC's that are not
up-to-date. Of course, if you happen to have admin. privileges on these
machines, then you can carry out this task as well. These types of updates
should be done in any event, whether or not an Access database is involved.
Now, if I install the front ends on their home drive...
Is their "home drive" a networked drive, or is it a local hard drive on the
PC? You really want the front end installed on a local hard drive. If these
are shared machines, you'll need to install it to a folder that everyone has
RWCD privileges to, since all users must have RWCD privileges to a folder
used for a JET database, whether it is the front-end or back-end. This would
likely require the support of your IT department, unless you happen to have
Admin. privileges on all PC's.
Tom
_________________________________________
:
I came across a stumbling block today with regards to the database
implementation. The IT Dept are now going back on their word. I hate asking
you thousands of questions and so, I have posted a question in the
microsoft.public.access forum - i'm going to start using it again now my
girlfriend and yourself have brought my attention back to it.
Here's my dilemma and posting in the NG:-
"I am currently getting help by one of the fantastic members of this forum
(Tom) with a multiuser database I am trying (in vain) to put together.
I have just been told today that the IT Dept at my workplace does not
support MS Access (no reason given). It permits its use, but doesn't support
it technically.
Now, my database has been split into a front end and back end. It will be
used by various users, all who have access to their own home drive and a
departmental drive. Now, as far as I'm aware, that is all they have access
to. There will be users from various depts using the database and so, some
will have access to, for example, F:/ and others won't.
Now, if I install the front ends on their home drive, can I install the
backend on any other drive, for example, Z:/? Even though they don't have
direct access, will MS Access weave its way through the realms of cyber world
and locate the back end?"
Just thought I would let you know mate.
Take it easy,
Neil
