>Naomi
>
>I dont understand this
>
>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.
>
>then we need to embed the images into HTML using data:uri format. Do you have an example of code to do this?
>
>The client will not have access to the server holding the images - they are on my server. I am sending the contents of the dbf to my client as a htm file - and I have to send the images sorry to be so slow on this but this is all new to me
>
>By the way, have a good Passover
>
>Colin


Happy Passover to you too! This is the first time in my life I'll be celebrating it in Israel!

If you send HTML, you can embed the files into that HTML directly (see this blog post, for example: http://www.bigfastblog.com/embed-base64-encoded-images-inline-in-html) In other words, you need to have your images in base64 format and then you would not need to send images to the client, they will be embedded into HTML.

I'm doing it in our C# ASP.NET MVC application, I think it is relatively simple to create such strings in VFP, hopefully someone will chime in with the exact code.