>>I am still looking for more variability since the current system binds the images into the executable making it a bear to change.
>
>Lemme expund on that. You could store all the bmps in a table, using FileToStr() to get them in a memo field, and StrToFile() to get them out. Then, just point teh report to a file name, and StrToFile() to the same filename. You could build the DBF into the EXE if you want at that point.

I'm not all that sure it would work. VFP caches images, so it may not notice at all that you replaced the file on disk. It can be forced to reload the picture using Clear Resources command, but then it may be an overkill - it would reload all other pictures currently in use, as well.

General fields may be a major PITA if you try to keep them in a table, specially regarding maintenance, but the 'create cursor, add a general field and stuff whatever you need in a general field' works like a charm, even in VFP5. OK, you're using more disk space, but it's returned in the end, and it's not expensive as it once was.