Access nightmare

[Sl33py]

I have a customer that uses an Access 2003 database, the guy that programmed it passed away and nobody knows what or how he did it.

I don’t know how to program in access. There is data in 3 different places ,they say the all work of the server.
The folders are different on each pc and the file sizes are different yet if you change something it updates everywhere

Server
Medilite\ – Healthcare 2003 5200kb
Medelite 2003 32916kb
Irene:
C:\Healthcare\ – Healthcare 2003 4600kb
- Healthcare_Backup 326812kb

Zianda:
C:Medilite\ – Healthcare 2003 5660kb
- Healthcare_Backup 20284kb
CalC98.
HSLogo.gif
Ltbrush.gif
MSCal.OCX
Newmu.
PkZip.
Schema.

We need to reload a pc but I can’t get the data base to work on another pc, it opens it but it does not update or search.

What is the correct way of sharing a 2003 database and working from multiple pc on it?

 

[werfie]

I think those are front end databases. So they are just used for the GUI. Inside of them, there will be linked tables that link to a Raw Data DB on the server somewhere, make sure it is not through a mapped drive which needs to be remapped after the format.

 

[graviti]

I have a customer that uses an Access 2003 database, the guy that programmed it passed away and nobody knows what or how he did it.

I don’t know how to program in access. There is data in 3 different places ,they say the all work of the server.
The folders are different on each pc and the file sizes are different yet if you change something it updates everywhere

Server
Medilite\ – Healthcare 2003 5200kb
Medelite 2003 32916kb
Irene:
C:\Healthcare\ – Healthcare 2003 4600kb
- Healthcare_Backup 326812kb

Zianda:
C:Medilite\ – Healthcare 2003 5660kb
- Healthcare_Backup 20284kb
CalC98.
HSLogo.gif
Ltbrush.gif
MSCal.OCX
Newmu.
PkZip.
Schema.

We need to reload a pc but I can’t get the data base to work on another pc, it opens it but it does not update or search.

What is the correct way of sharing a 2003 database and working from multiple pc on it?

More than likely is that you have the folder on the server hosting the file "Medelite 2003" shared, and mapped on the clients machines. The "Healthcare 2003" file is then copied to each machine.

From what I can see, the "Medelite 2003" file is the only unique database file located on the server only. So this would be the database actually storing the data itself. The "Healthcare 2003" file will contain the frontend, or all the Forms for the user. This file is then copied to each client and linked back the the "Medelite 2003" file, using table linking. Ideally a mapped share to a particular drive letter is made on each machine (Lets say I: for arguments sake). Then the "Healthcare 2003" will look for "I:\Medelite 2003.mbd" for the linking. Then you can copy the same copy of "Healthcare 2003" to all the machines and it should all work.

This is a rubbish way of using databases, but is a common enough practice unfortunately. Especially painful when your datasets start getting quite large.

To solve your problem, start looking at the content of the databases themselves. If I'm right, the Medelite will have a large number of tables, whereas the Healthcare 2003 will have a minimal amount, if any, and will contain a lot of queries, forms and reports. If this is the case it will be as simple as figuring out if they were using mapped drive or UNC paths, and then setting up the new machine with the correct table links.

HTH

 

[SirFooK'nG]

There is a master mdb on the server and the others are all probably linked using the linked table manager... thats my guess. So the User has a Front end (GUI) basically for inputs etc. If the tables are linked, then run the linked table manger and try link it manually again with a new location (where the master resides) to restore the links.

 

[LPCPT]

Make sure you charge them a lot. That way they will soon realise that outdated methods should go. Anybody still using access for a business system should really catch up

 

[biena]

Who wants to bet that this database is not even backed up. If nobody know what the infrastructure is then any disaster recovery is going to be a nightmare.

 

[Sl33py]

More than likely is that you have the folder on the server hosting the file "Medelite 2003" shared, and mapped on the clients machines. The "Healthcare 2003" file is then copied to each machine.

HTH

I coppied one file cant remember now which one and it complained about cant find J: the other one complained about K: so I think you are on the right track here.

 

[Sl33py]

Who wants to bet that this database is not even backed up. If nobody know what the infrastructure is then any disaster recovery is going to be a nightmare.

I do a image of the server to a external, I use cobian to backup to a spare hard drive and then I use delta copy to backup to my local server...