Hi,

Running Pdox9 under XP.

The error comes up when trying to create a new report.

File/New/Report/ leads to unexpected GPV (violation)

I tracked this down on bertil's site. It tells me to install service pack 1
before 2.

I had already installed Service Pack 3 in any case. Any suggestions please.

--
-----
Anne Wainwright
Please reply to group

Anne,

This error-message is a fairly generic one, in the sense that an "access
violation" simply means that the program fell-down and there could be many
reasons for it. First of all, dismiss the various websites that
scream "virus! virus!" If you're technically curious, here's a good site
that explains what this (and a great many other) messages mean:

http://www.icla.be/us/bc_messages02.htm

(It's specific to Delphi but it still gives a good overall explanation.)

With a message like this one, you look for common-factors in the symptom(s),
and in your case the clear best-guess culprit is "reports." Or it could
have something, more likely, to do with your printer-setup or maybe the
lack thereof. Here are some things to try:

(0) "What changed?" Besides the service-pack, besides Paradox, and
discounting (for now) the presumption of "virus, virus!"

(a) Restart the machine from power-off if you have not yet done so.

(b) Re-select the default printer in the appropriate Windows control-panel.
Print a test page.

(c) Review the report-related settings in Paradox, including the
printer-related defaults. Paradox can render things "for the printer"
or "for the screen," for instance. It is very intensive in its use of the
graphic subsystem of Windows.

(d) Evaluate the performance of existing reports. Do they work?

(e) Explore variations: can you build and print a report that does not use
any sort of data-model? Exactly /when/ does it "all fall down?"




----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com

Sundial Services <info (AT) sundialservices (DOT) com> wrote in
news:45bcb912 (AT) pnews (DOT) thedbcommunity.com:


Thanks for tips.

This error was similar to one last year which again reared it head a few
days ago in that I found I could not create the report on the form code
using View | Document Source (when in code editor of course) and bells
rang.

The solution to both problems strangely revolves around the installed
printers. Previously deleting the printers as recommended solved the
problem. Being more circumspect this time around I found that changing
the default printer solved both problems. Changing this back to the
original default did not subsequently recreate the problem.

Thanks again to Gunter who helped me solve this last year. Any ideas on
why this happens and what could be done to prevent this welcome.

Anne



--
-----
Anne Wainwright
Please reply to group

Hi,

Thanks for tips. (reposted with this at top. sorry, Xnews defaults to
bottom posting).

This error was similar to one last year which again reared it head a few
days ago in that I found I could not create the report on the form code
using View | Document Source (when in code editor of course) and bells
rang.

The solution to both problems strangely revolves around the installed
printers. Previously deleting the printers as recommended solved the
problem. Being more circumspect this time around I found that changing
the default printer solved both problems. Changing this back to the
original default did not subsequently recreate the problem.

Thanks again to Gunter who helped me solve this last year. Any ideas on
why this happens and what could be done to prevent this welcome.

Anne
Sundial Services <info (AT) sundialservices (DOT) com> wrote in
news:45bcb912 (AT) pnews (DOT) thedbcommunity.com:

-----
Anne Wainwright
Please reply to group