I have a array of various applications that I support, they range from Access97 through VB6 to C#. Primarily they are Vb6. Last time I did a head count I had 43 separate vb6 applications.
I mention all of this to illustrate that my ability to do sweeping changes is pretty much nil. Thus I can’t realistically change the applications to avoid the problem below.
On to the problem:
Most of the applications above pass information to Microsoft Office in one way or another. The most common is to query a database, format the data into a text file, label the text file as a .csv/.doc and then point the Office API at it and tell it to open the file.
The issue is with the relative paths created Cameyo. The vb6 app.path command is generally used to find this files, however the app.path command points at the location of the .exe in the virtual folder structure, no the actual folder structure. Thus, when office goes looking for the created file based on the app.path location it fails to find anything.
This can be solved by make turning on the Virtual Integration option, this creates a folder in the correct position and you can see the temporary file created by the application. What you cannot do however, is open it and neither can office.
Lastly the question:
Is there an option somewhere that I have missed that will allow external applications to open files inside of the Cameyo virtual folder structure?
