Updating a designed Access Database 2

[sstime]

I created a database for a customer and have been making changes, downloading and replacing the complete database. I am looking for some suggestions on how to update the database after it goes into production, since I do not want to replace their tables of employees, inventory, scheduling, etc. This will need to be done remotely since I am on the West Coast and the client is located in the Central U.S. I imagine that I will need to change or add a query, reports, forms, etc. on an on going basis.

 

[fneily]

Depends on what you mean by "an ongoing basis". You could have them put it on a citrix server (

http://www.citrix.com)

and then you can login remotely and make your changes directly to the local database.
Or you could have their's as a master and create a replica for yourself. Then after you make changes, have them sync it with their's.
Is it just one database?
Or FTP the file around.

 

[sstime]

I have been replacing the complete database by transfering it with PCAnywhere to a vendor in Texas. He then copies it to the clients P.C. location. At present, there is only one database, but possibly in the future, there will be multiple locations. I'm not sure, but I think the vendor in Texas will be setting up SQL Servers later. Since the database is completly Menu driven for the client, I was hoping there would be a way with a macro to wild card changes imported into the production database from a downloaded update database.

 

[fneily]

Have you looked at Tools - Replication - Create Replica?

 

[sstime]

I created a replica as you mentioned, but I don't see how this would solve my problem. Nothing in the repilca runs, macros halt, etc. and they do work in the master.

 

[fneily]

Quite bizarre. My replicas work fine. Have no idea. I guess you also read up on replication. When changes are made to the replica, you can then use Synchronize Now to update the Master.
In regards to a macro, have you looked at the TransferDatabase command? So maybe you could create a macro that will run when the user clicks a command button and your changes will be transferred over.

 

[sstime]

I'll look into the transferDatabase command. Thanks for you help, I was looking for a direction to take to resolve this issue. Thanks again.

 

[JoeAtWork]

Have you split the database into front and back ends? Because if you haven't, that is the first step. It allows you to change queries, forms and reports, and you just deploy the front end to your customer. The only thing they need to do is relink the backend tables.

 

[sstime]

Humm.. I guess I don't understand the consept of splitling the front and back ends of the database. Could you elabriate a little more. It sounds like a concept that would solve my problem.

 

[JoeAtWork]

You split the database into two MDB files.

Backend - has all the tables.
Frontend - has everything else. You link to the tables in the backend.

There is a wizard in Access to do this for you:

Tools -> Database Utilities -> Database Splitter

 

[sstime]

Thank you for all your suggestions, I now have some direction to proceed with. I learned alot with all this help. Thank you again, very much appreciated.