Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a C# application using OCX to open a local QVW in a form.
So far so good ![]()
I am struggling however, to open a document from the server.
My starting point is the URL I use in access point:
http://<SERVER>.com/<FOLDER1>/opendoc.htm?document=<FOLDER2>/<FILENAME>.qvw&host=<USER>@<HOST>.com
From that I get these components.
Rearranging this to a qvp path, I made:
qvp://<USER>@<HOST>.com/<SERVER>.com/<Folder1>/<Folder2>/<FILENAME>.qvw
Now when executed, I am at least prompted for a password.
If I enter an incorrect password, the app hangs & exists.
If I enter the correct password, my form control tells me that the file cannot be found.
So in a way, I feel I am 'close'.
What am I missing ?
The OCX-control is a scaled down/tweaked version of QV.EXE and follows the same syntax from opening docs from a server:

So I think you must leave out the <SERVER.>.com since that is the same as <HOST>.com and doesn't need/can't be specified twice:
qvp://<USER>@<HOST>.com/<Folder1>/<Folder2>/<FILENAME>.qvw
The OCX-control is a scaled down/tweaked version of QV.EXE and follows the same syntax from opening docs from a server:

So I think you must leave out the <SERVER.>.com since that is the same as <HOST>.com and doesn't need/can't be specified twice:
qvp://<USER>@<HOST>.com/<Folder1>/<Folder2>/<FILENAME>.qvw
Finally got it : "qvp://<server>/<folder2>/<Filename>.qvw";
Absolutely kicked myself how I worked it out in the end.
Simply 'open in server' from DT, where you can browse with an explorer.
After opening in DT, you can see the qvp path that it opened.
Just pop that path into your C#.
A few of things made this harder than should have been.
Of course, 1 of those might have been my lack of understanding.
Some of the QV documentation, like the one above, states NOT to put the 'qvw' extension in the filename - in my case it would not work unless it DID have the extension.
Again, some of the QV documentation does not make it clear, what it deems the 'host'.
My Access Point URL has a querystring called 'host', but in the end what actually worked for me in the qvp path, was to use the server name in the opendoc.htm path, as the host for qvp.
The other difficulty: the original file I was testing still does not work, but just about every other qvd does. I must have just picked the 1 that had something 'different' about it. But that's a job for 'tomorrow' to explore. I know it has some macros in it, so I am suspecting that might have something to do with it.
Thank you Petter for your relentless tolerance of my noob questions.
Hope the above if of some use to someone else on day !
Regards
Simon
The QV documentation was incorrect for my case.
However, that's not your fault !
Your statement about QV.EXE using the same syntax, gave me the clue to my final solution (explaned in last post) - so for that alone you have saved me !
marked Correct