Using MDE files in a multi-user environment (Access2003)

[Guest]

I have successfully created several ‘single user’ applications as MDE files
to run on systems without Access installed. However I have several users who
want to use them over their networks in a multi-user environment, is it
possible to install an MDE file, containing the tables, on a server (as a
‘back end’), and install the forms and code etc, as an MDE ‘front end’ on the
various client computers on a network. Again I am assuming Access is not
installed on the server or the clients.
Malcolm W.

 

[Rick Brandt]

I have successfully created several 'single user' applications as MDE
files to run on systems without Access installed. However I have
several users who want to use them over their networks in a
multi-user environment, is it possible to install an MDE file,
containing the tables, on a server (as a 'back end'), and install the
forms and code etc, as an MDE 'front end' on the various client
computers on a network. Again I am assuming Access is not installed
on the server or the clients.
Malcolm W.

First off an MDE cannot be run without Access installed. What making an MDE
does is lock down all code based objects so their design can neither be viewed
nor altered. It does not create a stand-alone executable.

Otherwise what you are proposing is fine. The file with the tables need not be
an MDE since an MDE does nothing to tables and queries.

 

[Guest]

You would need Access on the server and have an mdb in a shared folder
(security issues with this method). Or SQL Server would be better.

 

[Rick Brandt]

You would need Access on the server and have an mdb in a shared folder
(security issues with this method). Or SQL Server would be better.

Sorry, but this is incorrect. When a split Access app is using Jet (mdb file)
to hold its data then the only place Access needs to be installed is on the
client PC. The server is "serving a file", nothing more.

 

[Guest]

Thanks for all the answers.
I am sorry I have not made myself totally clear on this.
I want to create a multi-user distributable Access run-time application,
(the MDE file type was incidental). I have done this successfully for single
users, and have also created multi-user solutions on networks with Access
running on all the client PCs, but I really want to be able to supply a
backend server with front-ends on the clients, with neither the server or the
clients running full Access. Is this possible?
I have Access 2003 Developer Extensions
Hope this explains matters a little better

 

[Rick Brandt]

Thanks for all the answers.
I am sorry I have not made myself totally clear on this.
I want to create a multi-user distributable Access run-time
application, (the MDE file type was incidental). I have done this
successfully for single users, and have also created multi-user
solutions on networks with Access running on all the client PCs, but
I really want to be able to supply a backend server with front-ends
on the clients, with neither the server or the clients running full
Access. Is this possible?
I have Access 2003 Developer Extensions
Hope this explains matters a little better

Again; a multi-user split app can have the back end sitting on any network
resource that all users have access to. That box is only serving the file. It
is in fact the equivalent of a shared remote hard drive. There will never be a
requirement that the server box have Access installed on it.

When you install a runtime app on a PC you ARE installing Access. The only
difference is hundreds of registry entries that prohibit using the Access
executable to create new files as you can in the licensed version. Once
installed a multi-user runtime app with a shared back end operates in exactly
the same manner as if all users had full-blown Access installed.

 

[Guest]

Thanks Rick - thats a lot clearer now!