Hi Richard,
I would somewhat-strongly caution against storing images in a TPS Blob.You are going to create a world of pain for yourself at some point in the future.
TPS files (ie the file on disk) maxes out at 2 Gigs. So basically what you are doing with this design is creating a built-in time bomb that will go off at some point in the future. And the bad news is that when it happens _all_ your pics will be lost.
A _much_ better idea is to store the pics as disk files, one file per pic, and then have a TPS file which contains the filenames of these pics. You might think this is harder to manage now but
a) it scales
b) it's really fast to backup (since you only need to backup new pics, and the tps file.)
If you did want to add the image to a Blob, then you need to consider that the pic is uploaded part-way through the form, but the new record for the table is only created when the user clicks on "save". So the easiest is to allow it to save to disk, then move the disk image into the blob after the record is created. In other words in the PostInsert / PostUpdate routines.
In those routines the record has been created (or saved) so you can assign the blob there, and do an UPDATE on the record.
Cheers
Bruce