deploying mde in network environment

[default105]

I have db that I have split and wish to deploy where I work. The mdb-be is
on a network drive and I want the mde to be located on the users computer.
It works if the person is the only user on the computer. If there are
multiple users on the computer I run into an interesting problem. I can open
it because I am the administrator of the computer but the other users are
listed as power users. The next person who logs on can open the mde but that
is it. I have tried to install the mde in the users/application directory to
no avail, I run into the same problem. I have asked IT about it and they say
it should work and is not a IT issue. Now I have not ever deployed a mde
before so I am probably missing a few(if not many) steps. It seems to be an
ownership issue but I did read online that legacy programs can be a problem
deploying on a multi-user machine. I do know that if I put the mde on a
server drive that anyone can open it but this is defeating the purpose. Any
help would be greatly appreciated. Thank You in advance

 

[Tom van Stiphout]

On Mon, 10 Mar 2008 18:36:02 -0700, default105

You did not mention what version of Access you are using.
In A2007 the mde should be deployed in a Trusted Location (see help
file).
It could also be an issue with security privileges on the backend
location. Note that all users need to have the ability to create files
in that network share. WIthout it, Access runs in single user /
readonly mode because it cannot create the LDB file.

-Tom.

 

[Matt]

Is your database (seperate from your intranet) set up on a workgroup? That's
what it sounds like to me. I am doing precisely what you are attempting and
it works like a charm. I'm able to just e-mail out mde updates when I'm
ready and move on.

 

[default105]

Access 2000 database. Most current version we have at our plant. It is
located on our public drive (X) but the problem I have is when it is
deployed on a single machine with multiple users. This is where the problem
starts, if I have it install in My Programs/DatabaseName or Documents and
Settings/All Users/etc , then an ownership issue seems to arise. I was
trying to avoid having up to ten + mde's installed on the same machine.
Maybe this is the problem that I have to deploy it to everyones inside
everyones own profile in order for the issue not to happen. I have tried to
email out updates but that has caused some problems because some people save
it in a different location or do not update their shortcut to it. I have
found the creating an installer and deploying solved the issue because I can
have it overwritten if the file on the machine is older than what is inside
the installer. This has been frustrating to say the least. Sorry for such
a lengthy answer and I hope I have provided enough information.

 

[Matt]

You have it split, correct? Just place the BE in a shared folder on the
network, and send out the new .mde files to everyone. I have everyone here
place it on their desktop, so everytime they download the new one, it
overwrites the file so there is no link/shortcut problems. As for several
different people using the same computer, if everytime someone is finished
they close the .mde, then the next person getting on would have to log into
it under their own username (assuming that you do have the workgroup setup
INSIDE Access). Would it be feasible to have a generic windows log in that
they could use, then use different user names inside Access? Aside from
that, I don't know another way around having several copies under each
individuals log in. We keep all of our My Documents targeted to the server,
if you have the same setup, you could just have them placed in their My
Documents. Hopefully something here will help.

 

[default105]

Thanks for the response and the help. Here is how it is set up

mdb-be is on the X drive
mde-fe is on the users computer installed to program files on C drive.

if the computer is a multiuser, which where I work if you are caught on a
computer not logged on as yourself, it is grounds for dismissal, anyways.
After the installer is run, if John logs on first and uses the mde-fe, then
logs off, then Frank logs on, Access will open and state the Johns profile
has ownership of the file and will not open it. This is the problem. In
fact if I transfer it from a thumb drive (copy it) to program files as the
administrator, it will open for the first logged on user but not the second.
But if I place the mde-fe on any of the network drives, each and every logged

 

[Matt]

Maybe it's a user rights thing. Being on a network drive, users might have
inherited access rights to it. I tried but could not replicate your issue.
When you open up your mde does it ask you for a username and password? I
logged off and back in as someone else, and had no issues. BUT, I did have
to reset that users rights on my computer (not the network rights) because he
didn't inherit enough privelage to edit anything on my harddrive, so it
opened up as a read only; but it opened up nonetheless.

 

[default105]

Sorry for the long awaited response. Yes, I have the problem with being read
only. However, it is the code that runs that stops the loading process. The
users should have full access to their My Documents folder so I will try to
deploy it there. I do not have the read only warning that access gives you
on the first user but it only happens when the second user tries to run the
mde. I think I have narrowed it done to the "take ownership" flag in the
security preferences, but I find it odd that every user can run most programs
in the programs files directory and not have this issue. Thanks for you help

 

[viktor chuzhakin]

Sorry for the long awaited response. Yes, I have the problem with being
read
only. However, it is the code that runs that stops the loading process.
The
users should have full access to their My Documents folder so I will try
to
deploy it there. I do not have the read only warning that access gives
you
on the first user but it only happens when the second user tries to run
the
mde. I think I have narrowed it done to the "take ownership" flag in the
security preferences, but I find it odd that every user can run most
programs
in the programs files directory and not have this issue. Thanks for you
help