Chris,

I would suggest you lose the general field completely. There is more than one disadvantage to using them to store pictures (I will share those reasons if you need them).

The method in FAQ #7862 does not use a general field. Perhaps it is a little unclear, since it says "Use a character field or memo to store the path to the image." In reality, you need to store the name of the image file, including the path.

To see how this works, create a simple table from the command window:

create table test1 (descrip c(20), picfile c(20))

Browse the table and append some records; put in some descriptions and in the picfile field put the names of some of your .JPG files (including path).

Create a report, dropping a field on the report for the descrip field, and a Picture/ActiveX Bound Control for the picfile. Type in "picfile" (without the quotes) next to Picture from File.

If the new table is currently selected, you should be able to preview and print the report from inside the report designer.

Note that point #4 in the FAQ is very important. I have a .JPG called nopic.jpg, that I put in my report cursor at print time for all records that don't have a picture.

Let me know how this works for you...

>
>Thanks for all the questions. I think the one answer that is relevent here is that the picture gets stored into the General field as an JPEG "icon" or so it appears. I have both the path of the picture in the dbf and the General field.
>
>The FRX is correct because it prints correctly when the file in the general field is correct and prints the JPG icon when the general field contains this value.
>
>Could be abandon the General field and just read the path for the file? If so, do you have an example....I'm a little burned out on this headache.
>
>Hope this gives you some direction.
>
>Chris