>Craig states "...you don’t have to refer to a disk file ..."

>That is what I am curious about. Disk files, Blob fields etc all require that the file >is read from disk at runtime. This is not what he says. Even a Blob field is data that >will be stored somewhere.

>What I am trying to achieve is to display the bitmap using the PictureVal property >WITHOUT" going to the disk at runtime.

You got the wrong idea, that you could store the image within the PictureVal Property if you set that at design time. Nah, you need to set the PictureVal property at runtime as usual. But you don't need to refer to a file on disk, you can also refer to a table, more precise a blob field.

So if your concern is to store the picture into your executable, then store it in a blob field within a free table, don't exclude that table from compilation and then at run time open that table and set the pictureval to it's blob field.

I think you are true in using FILETOSTR() is also possible! So maybe try to include the bmp file in your project in the section Other/Other Files and don't exclude that from compilation. Then .Pictureval = FILETOSTR(yourpic.bmp) would also work and would read yourpic.bmp from within the EXE. Haven't tried though.

Bye, Olaf.