References - in variable locations (with mde file)

[CutAndPaste]

I'm creating an App in Access 2000 which will be deployed as an mde in a multi user network. Since the initial build, the Client has now upgrade some PCs to Office 2003.

The problem is that some machines use differing versions of Access, either 2000 or 2003 (the 2003 machines can use the 2000 version with no problem with conversion etc). Consequently the location of some of the files I need to reference (usually MS Word library) vary on each PC (e.g. some ref are stored in "..../Office" and some in ".../Office 11" Is there a way of allowing these to be set from each PC? via a field in a form for instance?

How would I approach this (short of getting the client to use the same version of access on all their pcs!). I had thought of copying all of the required reference files into the installation folder and setting the references to them there but this doesn't sound like an elegant solution - though it is simple ;-)

Cheers,

Simon

Simon

 

[Mile-O]

I have a similar problem as A97 and A2002 are used in my office.

What I do is develop in A2002 and then, once complete, I convert the database to A97 and fix any wayward references. In A97 I split the database and make an MDE from the FrontEnd. I then convert my .mdb frontend into A2002 and, if necessary, fix the references again. I make a 2002 MDE. So, depending on the users version I can distribute either an A97 or A2002 MDE and both link into the A97 BackEnd.

 

[CutAndPaste]

Mile-o-phile

Thanks, so it sounds like a pragmatic rather than a programmatic solution then!

Thanks,

Simon