Client/server application management

[Darrylles]

I've inherited an Access application where all tables reside on a server, but all other objects (forms, reports etc) reside on each of 10 clients.

Before anyone states the obvious; yes I need to get everything onto the server, but for the short-term does anyone have any tips about distributing objects to all clients?

It is currently very long-winded, particularly because copying 'changed' objects that already exist on the client renames the NEW object rather than renaming the old or over-writing the old.
This means that I have to go into each and every client, delete the old objects, then import the changes in!

Any help will be much appreciated.

ATB

Darrylle

 

[dannyocean]

Move everthing to the server and place where all users have access. Then apply user level scurity and create a shortcut. I do this on the server and have no problems. The user level security keeps from having writing conflicts. This way you only have to update the server copy.

Hope this makes sense.

Danny

 

[Chopper]

Whenever I have to put applications on user's machines and need to send out updates, I do the following:

1. Import your new objects into an blank database (your update database)
2. Put an AutoExec macro in that database that runs a code module.
3. In the code module, add code that exports the new objects to the user's database.
4. Pop up a message box saying the transfer is complete.
5. Quit the application.

Email a link to the update database on the server to all your users, or go to their machines and execute it.

When you export the objects to the database through code, they will replace the old objects.

Enjoy. -Chopper