We use VPE via the DLL interface from a 4GL. All has been OK until we moved to XP from Win2000 a few weeks back. We have noticed that the preview was taking a long time to appear.
A debug trace of our application shows that the VpeOpenDoc call was taking 20-30 seconds to complete and return to the application.
Is there a known issue with VpeOpenDoc under XP or is there something that needs to be done?
VpeOpenDoc
Moderator: IDEAL Software Support
8 posts
• Page 1 of 1
VpeOpenDoc
by downunder » Sun Jan 09, 2005 1:31 pm
- downunder
- Posts: 2
- Joined: Thu Dec 09, 2004 11:03 pm
by IDEAL Software Support » Mon Jan 10, 2005 1:35 pm
This issue is not known. However, do you have a default printer installed under XP?
Regards
Thorsten Radde
IDEAL Software GmbH
Regards
Thorsten Radde
IDEAL Software GmbH
- IDEAL Software Support
- Posts: 1633
- Joined: Thu Nov 18, 2004 4:03 pm
by downunder » Tue Jan 11, 2005 8:17 pm
Thorsten
You hit the answer.
I did have a network printer setup however something disconnected the printer. I did a Windows Security Update and that may have done something.
As I was only previewing the reports and not printing it was not obvious there was a printer issue. Your answer made me check a bit further and that seems to have fixed the problem.
Does the engine behave this way if there is a printer problem?
You hit the answer.
I did have a network printer setup however something disconnected the printer. I did a Windows Security Update and that may have done something.
As I was only previewing the reports and not printing it was not obvious there was a printer issue. Your answer made me check a bit further and that seems to have fixed the problem.
Does the engine behave this way if there is a printer problem?
- downunder
- Posts: 2
- Joined: Thu Dec 09, 2004 11:03 pm
by IDEAL Software Support » Wed Jan 12, 2005 12:38 pm
The same delay would occur, if you hit the print-button in any other application, because Windows tries to find the default network printer with a huge timeout.
What VPE does in OpenDoc() is to retrieve some information about the default printer. Internally some Windows API's are called which incorporate the same huge timeout.
Regards
Thorsten Radde
IDEAL Software GmbH
What VPE does in OpenDoc() is to retrieve some information about the default printer. Internally some Windows API's are called which incorporate the same huge timeout.
Regards
Thorsten Radde
IDEAL Software GmbH
- IDEAL Software Support
- Posts: 1633
- Joined: Thu Nov 18, 2004 4:03 pm
VPEOpenDoc network problem
by finn » Tue Dec 19, 2006 2:12 pm
We use VPE to display various documents to the user. But if the local network is disconnected or disabled (due to a VPN connection), the default printer is not available, and the VPEOpenDoc call will take very loooong time (10-20 seconds on my computer).
Is there any way to avoid this problem? Or will IdealSoftware in the near future have a solution?
Finn Rasmussen
Is there any way to avoid this problem? Or will IdealSoftware in the near future have a solution?
Finn Rasmussen
- finn
- Posts: 1
- Joined: Tue Dec 19, 2006 2:02 pm
by IDEAL Software Support » Wed Dec 20, 2006 8:10 pm
This is the same problem as above.
The next major release of VPE will not query for the default printer in OpenDoc(), so the timeout will be gone.
Regards
Thorsten Radde
IDEAL Software GmbH
The next major release of VPE will not query for the default printer in OpenDoc(), so the timeout will be gone.
Regards
Thorsten Radde
IDEAL Software GmbH
- IDEAL Software Support
- Posts: 1633
- Joined: Thu Nov 18, 2004 4:03 pm
by IDEAL Software Support » Fri Oct 12, 2007 1:08 pm
This is not a bug (at least not in VPE). The problem is fixed in v4.0 and higher.
- IDEAL Software Support
- Posts: 1633
- Joined: Thu Nov 18, 2004 4:03 pm
8 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 18 guests