Steve,
In general , GPF's are notoriously difficult to debug because they contain little direct information regarding the underlying problem.
However, there are a few things I've seen cause GPF errors:
1. Forms and reports that have invalid stylesheets associated with them. While you may not use sytlesheets directly, Paradox always saves stylesheet references with forms and reports. Thus, we need to verify that stylesheets are appropriately defined. See
for more information and related articles.
2. Forms and reports that've been saved with active filters or ranges. To check this, you need to open each document in a design window, choose Format | Filter, clear any criteria that appear in the filter fields, and then save the document. Once you've done this, the problems should disappear.
3. Running Paradox on a version of Windows based on Windows NT (such as Win2K, XP, 2003 and so on) without disabling certain configuarion defaults. See
and
for details.
4. Not attaching your printers to LPT ports. Recent versions of Windows let you share printers using UNC paths. In certain cases, this causes problems for Paradox. You should, instead, attach network printers to local LPT ports and print to those local ports.
Hope this helps...
-- Lance
