Are the files listed in a PBR that accompanies the application?

If not, try creating a PBR file and listing all of your graphic files in the PBR. 

In the worst case, you can then simply EDIT the PBR and CHANGE ALL on the directory name.

Olan

You can use relative paths in your code. Use this relative paths also in the PBR.

Add the folder where the graphic files are located to the App Path in the registry for the IDE. For 2017 the registry key folder is:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\App Paths\pb170.exe

Expanding on Roland's answer: After adding the path to the PB170.EXE registry entry, make sure all of your references in the application have no path, and the PBR has no paths in it either.

During runtime, PB will find the images because of the path, and during compile they'll be found and included in the EXE.

Hi Tracy,

Out of curiosity, what version of PowerBuilder are you doing this with?

Regards,

Hi Tracy;

   What I do is keep all my images in a sub-folder to the main working App folder when developing, testing & running under the PB IDE. I use "relative" path addressing for every image. So for example a picture, icon, etc could be:  ".\Images\tracy.png".

PBD / DLL. The PBR has no path references in it for any image. So at the end of the compile, I can copy the App EXE & its PBD/DLL's to a deployment folder then, copy the lone PBD/DLL in the "images" sub-folder also to the deployment folder.

 "tracy.png". Now the App EXE at run-time gets all of its images from the PBD/DLL that contains them. This is all done via my framework - so this coding approach is always ready to implement with no extra coding at the PB App side. Just follow the ".\Images\xxxxx.xxx" approach.

Food for thought.

Regards ... Chris