I would like to have the ability like "image box" that can display documents (ie: .pdf, MS Word/Excel, or other documents). 

Currently I have to save documents as .pdf, then save as .jpg before it can use in image box.

Thank you!

Faithlee,

Why not let Sesame have the operating system that you use do the heavy lifting.

If your operating system is associated with the type of file you are trying to open just use something like @AsynchShell to call it.

In my case I have a specific folder that I store my word files and a specific folder were I store pdf and other set places for other types.

I then have Sesame using Sbasic on a button, open it.
You can also have Sesame name it and put it in the directory and have sesame check and tell you if a document is available when you enter the record.

In my code example below it checks to see if the document is there and opens it if it is.

Var n as int

iF      FileExists(@ClientLocalValue("pathVariable")+"sesame\script\done\"+ptid+"script.
pdf") // needs to be changed based on working directory

// opens and displays the pdf
n = @AsynchShell(@ClientLocalValue("pathVariable") + "sesame\script\done\" + ptid +"script.pdf")

Let me know if you need additional clarification.

** Steve responded while I was typing so this is pretty much a duplicate response to his.

Thank you BobScott and Steve. 

If I can't find another way, then I will consider adding a text field as Steve has suggested.  Right now, I think it is not as user friendly.

I really like how the image box allows users to find the file and link to that file, without having the users typing in the path. 

Again, I really appreciate all your responses!

Faithlee,

The issue with a thumbnailed application viewer is not in the path to the file, or its resemblance to an image. The issue is in reading and interpreting an unknown file format so as to render that image. There are literally hundreds of thousands of file formats, many unique to their editor/viewer. Some are so unique as to be the proprietary property of the company that provides the editor or viewer. To give Sesame the ability to preview or thumbnail any file you throw at it, without regard to the format of that file, we would need to include libraries of routines that know how to read, interpret, and draw, virtually every kind of file there is. Even the operating system (I assume Windows of some ilk), needs to use the actual application, or shared library, from the company that provides that format, to render the thumbnails that appear in Windows Explorer. And, with all of Microsoft's resources, many formats are still rendered with generic images, rather than an actual preview.

That being said, you might consider using a set of representational images, rather than thumbnails or previews of that particular documents. For example, you can keep a list of all of the spreadsheet format extensions you intend to support: (.xls, .xlsx, etc..) and keep a static image of a grid or speadsheet. When the user selects a file that has any of the spreadsheet extensions you have in your list, your code displays the spreadsheet static image. You can do the same thing for other document types. That way there is no need to preview (read, imterpret, render, miniaturize) each and every document format you might want to support, and your users get a nice graphical representation of the file.