Packaging supporting files - how do I handle linked image files?

[tedmillerx]

I have a piece of software that I've built in Access 2002. It contains many linked image files. (If I embed them the application will be massive.)

I am using the Packaging Wizard to create a runtime version for my users.

My problem is that when my user installs and runs the application on their machine, none of the linked image files show up. Access is looking for them in the original location I created, but that location isn't being replicated during the user's install process. Right now they have to manually create the location Access is looking for and drag these supporting image files into it. I hope that all makes sense.

In the Packaging Wizard:
In the place where I 'modify install locations', I have tried setting the install location as:
$(AppPath)
$(ProgramFiles)
$(AppPath)\(linked location path)
$(ProgramFiles)\(linked location path)
- And everything else in the drop down list.

What do I do? I am hoping against hope that I don't have to change the location paths in all my reports for all these linked images. Even if I did this, it would not solve the problem if my user decided to install the program to a non-default location of their own. Help!

 

[tedmillerx]

Okay... I think I may have solved the problem myself. In the packaging wizard I have set the install location to $(CommonFiles)\(location path). Now the images are showing up even when I install the program to a non-default location (i.e. drive other than the C:\ drive).

 

[tedmillerx]

Scratch that last. It doesn't work after all. I won't go into why I thought it was working - it has to do with knowing when your images are linked and when they're embedded, and with me being a moron.

Any help with this problem would still be greatly appreciated.

 

[Remou]

Is it possible for you to store the images in a subdirectory of the install directory, in which case you can use CurrentProject.Path & "\SubDirName"?