>>>>>what is the dbf format to hold an image
>>>>
>>>>If you are using native VFP tables, then do not hold image within the table but just the path to image.
>>>
>>>But I am converting the file to htm and I want to send it to my client with the image in the htm
>>
>>If you're converting this to HTML and only sending HTML to the client, then you can embed the image into HTML using data:uri format. You don't have to include the actual content of the image into DBF if the process creating HTML has access to the server holding the images.
>
>Don't think you phrased the last bit very well.
>If the HTML only contains a link to the image then the image needs to be available on a web server accessible by the client. Conversely, the process *creating* them HTML doesn't need access to the server....

Yes, I meant this. If the Client has access to the server holding images, then HTML will contain links to the images. If the client doesn't have access to the server holding images, but the process that originally created the html does have access to these images, then we need to embed the images into HTML using data:uri format. In both cases we don't need to store actual images inside the table.

Only if the process that will create the HTML will run on the client and we don't want to send the actual images with the application and don't want to share the images on the server accessible by the client, we may want to insert the actual images inside the DBF assuming that DBF only has a handful of rows.