In my experience with using an MDE to an Oracle ODBC
backend, save yourself a LOT of heartache and put copies on
the local machine. I had 3 weeks of corruption hell before
I did that. Yes, the data was not affected (except for
users frustrated with losing data), but it wasn't worth the
aggravation.
What I DID leave on the network share was the dedicated MDW
workgroup file. That way, you still have to have access to
the share in order to get the database to execute. Of
course, that is assuming that you have the user/group
security set up correctly.
--
Kevin Nechodom
University of Utah Hospital and Clinics
Kevin dit Nechodom ack hsc dit utah dit edu
"Call me paranoid, but I think you are reading what I'm
writing!"
Rick Brandt<ri*********@hotmail.com> 7/18/2005 9:32:36
AM >>>Jay Mack wrote: Hello,
I converted an Access application that used to have a
MDE front-end (distributed to each user) with a MDB
back-end on a share. It now has a MDE front-end with
linked ODBC SQL Server 2000 tables as the back-end.
Is it a bad practice to place the MDE front-end on a
network share instead of sending a copy to each user?
I want to do this as a form of cheap security, since the
network share has access control on it. Previously, the
MDB back-end was on this protected share. Are there
problems inherent with multiple users opening the same
MDE front-end simultaneously? I'd rather not check
user IDs inside the application and send out copies of
the front-end at this time.
It will be slower and will increase the chances of the MDE
getting corrupted, but since your data is in a server
database you shouldn't have to worry about corruptions
of the data like you would if the data were in an MDB
file.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
