Paradox Community
Search:

 Welcome |  What is Paradox |  Paradox Folk |  Paradox Solutions |
 Interactive Paradox |  Paradox Programming |  Internet/Intranet Development |
 Support Options |  Classified Ads |  Wish List |  Submissions 


Paradox Newsgroups  |  Paradox Web Sites  |  Paradox Book List  |  FAQs From The Corel FAQ Newsgroup  



Subject: FAQ:PdoxWin:Unusual Problems:2000.08.10
Version 1.2 (2000.08.10)
edited by Paradox FAQ Team
Reposted by Mike Irwin: 2001.05.25

====================
0. Introduction
====================

This FAQ offers some suggestions for some commonly
experienced problems with Paradox 9. These may be
termed "unusual" in that they seem to occur for no good
reason, and the appropriate "fix" is often the very last thing
you would think of doing !

If you have suggestions for further additions, please email
mirwin@voicenet.com, and they'll be reviewed for addition.

-------------------------------
 0.1 Legal Info and Disclaimers
-------------------------------

Paradox is a trademark of Corel.
Borland Database Engine (BDE) is a trademark of Inprise.

The information provided in this FAQ is provided "as is" and
is not warranted in any way. The information provided in
this FAQ is not endorsed or authorized by Corel or Inprise
in any shape, form, or manner. The editors claim NO
responsibility for ANY illegal activity regarding this file,
or as a result of someone reading this file.

You may distribute this file, as long as the copies are
complete, unaltered, and are in electronic form only.

-------------
 0.2 Feedback
-------------

Please send feedback in a Corel Paradox newsgroup or the
news:comp.databases.Paradox newsgroup to any of the FAQ
Team mentioned in the "FAQ: FAQ FAQ" document.
Please preface the subject of your post with the string
"PDXWIN FAQ" to alert Team members to the function of
the message.

Please specify the FAQ name and section number the
comment applies to, if any.

==============================
1. General Information
==============================

This is a collection of some of the more frequently-encountered
problems that are seen in the newsgroups, with some suggested
remedies. Please do not expect that these suggestions will all
work all the time.

========
2a. Configuration Files - .cfg
========
Problems

- While trying to set up a key lookup system with separate table
and own library, I ended up at some point with the message
"Access violation at address 3FD52B48 in module CRLUI90.DLL.
Read of address FFFFFFFF." Now, creating a blank form brings up
a GPV; the form expert peters out at its final message "Creating
the form may take a few minutes..." Opening a form in design
either produces above message (after fresh boot) or GPV.

- I get continual Paradox crashes, all at the same address

- My ActiveX toolbar has suddenly acquired a whole load of
new buttons. They all have inverted triangles, claim (tool
tip) to be the same button, but don't function at all.

Solution

Paradox 9 has some configuration files that can get corrupted.
When they do Paradox exhibits some very strange behaviour indeed.

The two files in question are the pdx*.cfg files in the
program\config subdirectory to the Corel suite directory.
The files are the Toolbar files and they will be recreated
when you restart Paradox.

Their names are:
PDX_EN_FULL_BARS.cfg
PDX_EN_FULL_SBAR.cfg

DO NOT DELETE pdoxwork.cfg !

==========
2b. Configuration Files - .ini
==========

You will notice that a pdoxwork.ini file appears wherever
you set up your :work: alias. This was designed to allow
you to customise the look and feel of the program when run
from different directories, but never worked very well.

Your PdoxWork.ini file should, really, contain just:

[Folder]

==========
3. Freeze on Changing Working Dir
==========
Problem

Paradox apparently freezes on changing the working directory.
This usually happens on systems using the Paradox Project Viewer.

Another fairly common ground seems to be the use of Novell Client

32. This surfaced in Paradox 8 and persists, to a lesser extent,
in Paradox 9. The same symptoms can also be triggered in Paradox
8 by taking a very large form between view and design modes with
some of the edit windows open.

Solutions

Upgrading to Paradox 9, changing your Novell Client (both
Microsoft and Novell make one, so try swapping), and replacing
your Project Viewer with an alternative (e.g. ProView, at
sheep.east.ru:8100/~menkin/paradox.html) can all have good
effects.
Best of all: don't use the :work: directory - it's an
anachronism.

==========
4. Bad Upgrade
==========
Problem.

After installing the patch for paradox 9 which came in the
Corel Service Pack (SP1 or SP 2), Paradox 9 won't open.
Part-way through the opening sequence one receives the
following:

pxpal32.dll file is linked to missing export
palrtl32.dll:DeleteTableRef."

Solution

A DLL file didn't update properly and there was an old
version left on the disk for Paradox to find. This may be
because the file was still in use when the patch was applied.
This is the reason for rebooting BEFORE applying the patch.

Try the update again making sure you don't have any other
programs open when you do it. Trying the update in Safe
mode would be another option

==========
5. BE incompatible with Windows 2000
==========
Problem

The windows 2000 upgrade report indicates that the BDE
Administrator in control panel is not compatible with Windows
2000. If you try and run the bdeadmin.exe program it gives an
error message.

Solution

This message is erroneous, MS confirmed BDE works w/ 2000.
This is a Win 2000 bug not a bug in BDEAdmin. You can safely
ignore the message.

==========
6. PFPS printing error
==========

With Paradox Runtime (usually) you may get the following
error message

Print Interface Setup Error
PFPS initiate fail

This usually ocurs when you run a report and then decide
what to print. If you give a direct ObjectPAl instruction to
print, everything goes well.

Solution

Run pfreg.exe from the programs directory under Paradox.
This will register the components manually.


==========
7. Paradox 9 and Windows 2000, SP1
==========
Thanks to Tony McGuire" <tmcguire@2prudential.com> for this
information.

I have been using the execute() command in Paradox since the
DOS days (run). I am currently using Paradox 9 on Win2000.
I have a scheduling program called AT2000 (AutoTask 2000).
I have been using it (and its earlier incarnation, LaunchPad)
for more than 2 years.

I recently installed Service Pack 1 for Win2000.  All of the
execute() statements within my Paradox scripting stopped
working (when Paradox was started from a scheduler). Paradox
loads, and evidently fires the execute() command (I get a
"True" return value), but the "executed" program doesn't
actually execute. The execute() commands I issue are fairly
near the top of the Paradox script.

If I start Paradox & the script from an icon, everything
works normally. If I start Paradox, then manually start the
script, everything works normally.

I found that if I added a {delay} command in AT2000 right
after the command that starts Paradox, everything returns to
normal (AT2000 allows multiple sequential commands for each
scheduled task).  Everything worked, as well, when I added a
command in AT2000 to "wait until this program finishes".

I DO NOT know whether this issue is specific to AutoTask; I
would suspect that it is not (we have someone here using
LaunchPad in Win2000 SP1 who is experiencing similar issues,
but not with Paradox).  My main intent is to alert anyone who
starts having the type of problem I describe with ANY program;
I don't even know if this behavior is specific to schedulers.
At least anyone out there using this program can get Paradox
to execute external programs regardless of SP1 for w2000.

I have alerted Cypress Technologies of this issue (for any
of you who might be using AT2000).

Editorial Note:
---------------

If MicroSoft have altered the way in which processes are
spawned in Windows 2000, then this may not be a failure, but
a "long delay". If so, then any command in the scheduler
will clear Paradox to be able to issue execute() statements
with immediate effect.


Paradox Community Newsgroups


 Feedback |  Paradox Day |  Who Uses Paradox |  I Use Paradox |  Downloads 


 The information provided on this Web site is not in any way sponsored or endorsed by Corel Corporation.
 Paradox is a registered trademark of Corel Corporation.


 Modified: 15 May 2003
 Terms of Use / Legal Disclaimer


 Copyright © 2001- 2003 Paradox Community. All rights reserved. 
 Company and product names are trademarks or registered trademarks of their respective companies. 
 Authors hold the copyrights to their own works. Please contact the author of any article for details.