Above, is a list of images found in your application. Assuming default, .RED settings, one of the things that makes an application less portable than it might be is referencing images that are not in your / accessory / images/ directory, since Clarion stores such images in your app with a path name, and anyone trying to compile your application on a different machine may not have those images on that particular path.
To make your application more portable, configure CHT's ApplicationImagesEx template to copy all the images in your app to a standard location or to the / accessory / images/ directory so they're all in one place instead of scattered all over your drive.
Clarion templates, however, are not given write access to your screens in order to remove embedded paths automatically from the image names. So it is in your interest to maintain application portability by checking for images with embedded paths and removing the path which will no longer be necessary once the image has been copied by the template to / accessory / images /.
Images listed above, showing a path, are candidates for your attention. As long as a path is part of an image's description, inside your application, it will cause a hassle for you should you want to move the source application to another system or to a client's computer.
To remedy, go to the procedure or template named and remove the path from that image. To automate the consolidation of such images into a single location on your system.
See the "List And Copy" dialog on ApplicationImagesEx if you haven't already done so.