Hi Barbara

I am trying to not have extra graphic files about.

The issue comes about where one has a distributed system with local versions of the software. It is relatively easy to have a loader program where one detects the version from a central point and then updates ones local version as necessary. This doesn't require any extra mechanism for additional 'loaded' graphics (or other resources) used in such classes as the 'outlook' class when one adds menu items

What I dont understand is why I can display/print graphics from a table in a report but cannot do the same on forms. I guess the mechanism is different.

I also don't understand why VFP stops short with general fields (i.e. why there is no function to return what is stored in them or why one has to append from a file rather than a memory variable).

In the same way, why must my graphic be from a file (unless it was compiled with the project). Why can it not come from a memory variable? What is the difference between loading from disk and loading from memory? What is the difference between the object compiled in my project and a file on disk?

It all seems a relatively minor oversight that could be so easily rectified. Something for the wish list, I suppose.

If I cannot load from a file (binary memo or general field) or a memory variable then I would like to be able to point to a resource file (graphic or otherwise) that I have added to my project and get my graphic object to load that. Only, I cant figure out how.

Any ideas?

Regards
Geoff Scott

>I'm sorry, but I don't understand what the issue is here. What can't you load at runtime by storing the path and name of graphic files versus storing the graphic file itself? Can you explain specifically what you are trying to do?
>
>>Hi Barbara
>>
>>Yes, I think you are both right. Problem is I was/am using a class (modified outlook) which loads it's graphics at run time. I was/am trying to find a way to have the best of both worlds but cant figure out a way to load graphic images out of a file with all my graphics in it.
>>
>>I suspect I will have to sub-class the main button class and include the graphics that way. My main concern is to leave the system as flexiable as possible.
>>
>>Regards
>>Geoff Scott