>>>But since your image fields already contain the actual file, your best bet is to dump them into temp files via strtofile() (giving them appropriate extensions, if needed), and keep the fullpaths of the filenames in the cursor off which you run the report, and change the option to "file name". Kill the temp files when done.
>>
>>This also sounds a big complex. Suppose I retrieve a cursor with 365 rows with 4 columns of pictures and 4 columns that contain just the filename (not the path) of the pictures. The image field does indeed have filetostr of the file.
>>
>>So, what is the correct way for me to print all the pictures from that cursor (I can retrieve that image field as a Blob or as a General field).
>
>Now it would depend on what you use for reporting, how does it like its files served. If fox, you can set path to a folder, create all these files in it and forget about full paths. If it's an external app, like Office or Crystal, it will need full paths or there's no guarantee it will be able to find the files.
>
>So create 1460 temp files with strtofile(yourimagefield, filenamefield). In case you've dumped them into a subfolder you just created, this becomes strtofile(yourimagefield, fullpath(forcepath(filenamefield, lcYourSubfolder))). Then you delete everything in that folder and remove the folder itself - easier than memorizing 1460 filenames. Of course you'll have four of these, if you have four pairs of such fields.
>
>Printing calendars for the skiing season, are we? :)

Well, it says 'Daily Ticket Codes' and I have no idea what exactly does it mean or where these codes are used. I guess I can find out (ask around). Perhaps I'll ask James now.

In any case, what do you think is better - your solution or blob printing solution based on Craig's idea?

Update. Tried to call James and then Patty (she is a new tester) and didn't reach either of them. I can keep calling other people, though, just to satisfy my and yours curioisity.