There's a form with a general field that's bound to a JPG.
There's a table (SURVEYOR) that holds: char FOTO field - string of full path to JPG (including the name.jpg), and:
general field FOTOGEN - JPG file

On the form the JPG photo displays OK. When trying to print out a label, that includes the photo, get error "must be bound to a general field"

The label field's properties are set to FILE - ( SURVEYOR.FOTO) - including the brackets to give a name expr - i.e. the above full path.

This was working fine and when one opened the gen field one saw the actual pic. But now all one sees is the name of the file, e.g. Brian.jpg.

It's since moving to XP sp2 from sp1. On X2-clicking a jpg file we found that it's now displayed in "Microsoft photo viewer" or some such (whereas before it was "Windows Picture and Fax Viewer"). So the JPGs have become associated with the new software. When substituting for an older JPG the whole worked fine.

So we disassociated JPGs from the new and it all works fine again. This is OK for in-house use but, if a customer were to use the software, and have Xp SP2, and view their JPGs with this, it would screw up the system.

Essentially I'm asking how one would get around this. Is there some way of automating file association, away from this new evil, to ensure it doesn't happen again?

'ppreciate it

Terry