If anyone has any insights as to how to solve this problem, advice
would be much appreciated !

I'd written a custom application using OPAL in Paradox 10 on a prior
Windows XP computer which has been running flawlessly for several
years.

Last week we upgraded to new desktops and I installed Paradox 10 on the
new desktop, also running Windows XP. I installed Paradox 10 from the
Corel CD, moved over my "work" and "data" directories containing my
application's forms/reports, then set up the proper alias settings,
etc. Everything worked without a hitch ... until I tried printing
reports.

On my main form, I have a few menu dropdowns for printing different
reports. On a menu selection, the value in one of the fields is passed
to a Query which generates an answer to the PRIV:ANSWER.DB table.
After a sleep (1000) instruction, the values of the ANSWER.DB table are
passed to a precompiled Report which is sent to the printer, which in
my case is a locally attached (non-networked) HP Laserjet 1012.

This worked perfectly for several years. Now, on the new desktop I
after making my selection using the dropdown menu, it get the dreaded
Windows XP "Unexpected: General Protection Violation" chooing me to
"Abort", or "OK". Clicking either two doesn't resolve the problem.

In troubleshooting the above commands, I can verify that following a
menu selection, OPAL properly runs the query and places the correct
results in the ANSWER.DB table. If I then "manually" open up the
related report, (using "Project Viewer" or direcly using Windows
Explorer) the proper report is properly generated and I can print it
from there directly by choosing "Print" from the standard menu.

However, when OPAL is used to automate this process, it appears to
breakdown at the "print report" stage. I of course opened up all of
my forms and reports and recompiled (Ctrl+D) them on the new machine
but to no avail.

Has anyone run across this problem ? How have you solved it ?

Thanks in advance;

Andrew

Which service pack level of P10? Get the build number from the Help About
dialog.

In original release of P10, report.print("report.rsl") would cause a GPV.

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"andrewnp" <parfomak (AT) verizon (DOT) net> skrev i meddelandet
news:1161372685.839858.8620 (AT) f16g2000cwb (DOT) googlegroups.com...

I encountered the same problem with p7 32. Worked for years and than
would GPV on print, after moving to a new machine. Scratched my head
for a week. Turns out it was too many fonts. Don't know what the limit
is with P10 but do know that the newest windows machines have a lot of
fonts, especially XP media center. In my case the C:\windows\fonts
folder had 1200+ fonts. Reducing the count to less than 750 eliminated
the crash and everything printed normally. Who needs that many fonts
anyway?

This is a documented issue with P7 32. Again, I don't know if the font
limit is different with P10.

Randy


andrewnp wrote:

Thanks very much ! I installed the P10 Service Pack 3 and the problem
was instantly solve.

I do note for the other members of this Group that it looks like
anything earlier than WordPerfect 11 Suite isn't on the Corel Support
webpage. I was lucky as I had downloaded the prior hotfix and service
packs to a CD for P10, else I"m not sure if they're available.

- Andrew

Bertil Isberg wrote:

Andrew.. there's a complete list of SPs on the URL Links page on my web
site, and Bertil has a list posted on his site, too..

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards