ViP Designer problems...help! (ViP Specific)
At 08 JAN 1998 02:01:18PM Nik Shenoy/SYSINCT wrote:
I need to make some changes to an existing ViP application, so I dusted it off and now I am having all sorts of problems editing the code.
My first problem is that the report designer refuses to run on my NT Workstation, complaining that the printing system is not intialized properly. I have no problems with other applications (I can also print properly). It *used* to work before, but I have installed other software since then so I don't know how this got messed up. I tried reinstalling ViP 2.2 and it didn't seem to make any difference.
So, I gave up on that and installed ViP on a Win95 machine. That worked better, but now I get a crash everytime I try to edit the sort order of a report. Namely, "VIP caused an invalid page fault in module VRPUIN20.DLL"… This happens for all of the report objects I have defined.
How do I fix these problems? I can't install the 2.5 version because I am guessing that it will require a new runtime and I don't think I could get my client to deploy that at this point…
Nik
At 08 JAN 1998 02:51PM Stephen Bellefontaine Revelation wrote:
Hello Nik,
I have also received the error message "Your Print System Could not be initialized. Check your windows printers configuration and printer drivers" when trying to run a ViP report.
I have only seen this behavior when running ViP 2.2 on NT4.
I resolved the issue by selecting settings, printers, deleting the default printer driver I was printing to, rebooting, and then recreating it.
The Sort Order bug was fixed for ViP/DX 2.5. The development staff have released a patch for ViP 2.2.
For a quicker work-around, I would suggest that you post your email address so we can send you the updated .dll file.
Hope this helps,
ViP/DX Tech Support
At 08 JAN 1998 02:59PM Nik Shenoy/SYSINCT wrote:
Hi Stephen,
At 08 JAN 1998 03:00PM Nik Shenoy/SYSINCT wrote:
Hi Stephen,
My e-mail address is [email protected]. BTW, I did try deleting my NT printer, etc. I think it's not working because it is a network printer and I'm guessing ViP doesn't like something about the configuration of that network printer.Thanks...