Broken references when I move the db to a new server

[Access9001]

When I move my access databases to a new server, a lot of the code breaks on-run.

For instance:
Microsoft Office xx.0 Object Library
PDFCreator

Is there a way I can programatically remove bad references and re-add the good ones across all my databases?

 

[Access9001]

Still having trouble with this if anyone is kind enough to shed some light! Thanks

 

[boblarson]

You shouldn't have a problem with the Office reference if you are running this ON your machine and not ON the server. If you are running it ON the server then it might be because the correct stuff isn't installed.

Otherwise, the PDF Creator problem is likely because it isn't installed on the server (are you using Citrix or Terminal Services?) or the links for the database haven't been updated. You have to update more than just the linked table manager if you have had any code or embedded objects which refer to the server. It uses UNC paths for many of those items so when moving servers it can fail. I have a report which uses an embedded Word document for a map and it needs to have it's DDE Link updated each time it moves to a different server (we have Test, QA and Production servers).

 

[Access9001]

Using Citrix.

And yes, they just installed Access but I think it's the wrong version (I was using version 12, while only version 11 is available on the reference list).

Updating the links is fine as long as I can mass-automate it. For instance, be able to open up all my databases via a code loop and just tell it "Remove these missing references, add these following references" so everything else will work properly.

 

[boblarson]

Using Citrix.

And yes, they just installed Access but I think it's the wrong version (I was using version 12, while only version 11 is available on the reference list).

So the right version needs to be installed or else you will have to open the file ON the server, from the server desktop and then go into the VBA and uncheck the wrong reference.

And the PDF Creator needs to be installed on the server so the printer is there.

Updating the links is fine as long as I can mass-automate it. For instance, be able to open up all my databases via a code loop and just tell it "Remove these missing references, add these following references" so everything else will work properly.

Good luck - it is not a simple process to be able to do that. But perhaps if you get the two problems taken care of, the other stuff might not need to be fixed, depending on what you have in there. We have to go in manually and relink and update the other places the server paths are when we move between environments.

 

[Access9001]

I mean it may get to that point where I just have to do it manually... there are so many databases, though, so I really didn't want to have to do that.

 

[gemma-the-husky]

in passing - note if you use an mde, there is no way at all of updating references. you really need to design on the lowest platform you are likely to encounter.

access WILL resolve references upwards, but not downwards. so if you design in office/access11 (ie A2003) and distribute to office/access12 (ie A2007) all is well. It's just an issue when you go the other way.