Hi again Scott,

According to the information I have gathered, there are two a little different notations you would use, depending on whether your a opening a file on a local drive on the client or through a UNC share:

• file:///C:/SomeFolder/SomeFile.txt
• file://SomeDNS/SomeShare/SomeFile.txt

Note the double and triple "/", depending on what kind of file location you are accessing.

Using JavaScript window.open() however, has all kinds of complications regarding security, as I mentioned in my last reply. I didn't explore the problem and possibilities in details, as this is more of a JavaScript / Browser problem, than it is Visual WebGui, but what I did catch was that it has do do with the fact that your are trying to switch to another protocol, from within an active browser window (switching from http:// to file://), and the browser security is blocking that change. Some information can be found here.

I consulted with our leading developer and we agree on that, unless you are able to find a cross browser solution to this (apparent) browser security issue, then the best practice would be to have the user upload the file to the server and then serve it back to the browser via a Visual WebGui gateway.

I'm sorry that we are not able to solve your case the way you would like to solve it, but hope this can help you some.

Palli