Question MS Access 2007 & Windows Server 2008

abbaddon223

Registered User.
Local time
Yesterday, 16:25
Joined
Mar 13, 2010
Messages
162
Hi all,

I've forged on and got myself in a jam I think...

Basically, I've been building db's for small clients and got to the point whereby I need to have remote access to the db to carry out routine amendements etc.

So, where I'm at is that I'm renting a dedicated Windows 2008 server. My plan was to put the databases there, section off the server and give each client a login / password.

The issue I now have is that after uploading the db to the server desktop, some of the vba is playing up (looking for outlook, word etc that now isn't there due to the server desktop being very basic). Also, the look of the db has changed quite dramatically on some forms.

Does anyone know of a way (or better way) of me managing how both myself and my clients can access a db.

Many thanks for any assistance you can provide!
 
I have picked up this thread cause it still has not got an answer. I am not an expert but I will give you my opinion. If it is not the best or even incorrect then usually someone will chip in and say so.

There are probably more complicated ways of doing this but I will make a very simple suggestion as you are talking about small DB's.

First all your MDB should be split with a front end / back end.
The Backend MDB should be on a shared drive that both you and your clients have access to this back end has all your tables in it.

The front end is a MDB or MDE (compiled) but has usually only forms/reports/queries although you might have some tables in it. This mde file should be stored locally on the users computer.

Now have a look in the forum for how to do automatic updates to front ends. There are many methods of how to do this.

My preferred method is that I created an install script with AutoIT. This script INSTALL.EXE looks in the shared drive and copies the current .mde from there to their local computer. It also copies a open.exe script which I made with AutoIT. It is saved in the same place as the .mde but puts an icon on the desktop which is linked to the open.exe

When the user clicks on the icon it calls the open.exe which then checks if there is a new version (by date) of the .mde in the shared drive. If yes it copies it to the local computer and then open.exe calls this .mde. If there is no new version then it simply calls the .mde. The users has no idea.

With this set up you always develop your front end which links to the backend. Once you have made the changes you want you copy your new version to the shared drive. Because it is a newer date it will be automatically downloaded by the user the next time they start it.

Is this what you are looking for?
 

Users who are viewing this thread

Back
Top Bottom