Paradox for Windows Desktop has stopped working

I recently bought a new computer  (Core i7, 3.33 GHz, Windows 7 64 bit) and then installed and upgrade to  WP office X15, including Paradox 11.

I've been doing this kind of query of decades and had no trouble before.

Now,  when I make a QBE I get the usual answer table, but when I go to Query, Properties, Structure and change the query structure order and then  click the Run the Query button the following message appears:  Paradox for Windows Desktop.  Paradox for Windows Desktop has stopped working.  It says it will try to find a solution but never does.  Paradox then closes down.

Occasionally, it crashes as above when I only go to Query and then click on Properties.

I did a reinstall of Paradox which did nothing and also a reinstall of WPO5.  Still have the problem.  Every other function of Paradox 11 seems to work fine.

Any suggestions about how I can cure this problem? 

Thanks,

JG

When talking to the rep. while requesting a refund for WP Office Pro with Paradox 11 I was amazed (yes!) to learn that despite what the original sales rep. had told me, Paradox 11 is NOT compatible with Windows 7.  I won't rehearse my tale of woe, but in the off chance that anyone reads this, take my advice and don't buy WPOX5 with Paradox if you're using Windows 7.

Adios,

JG

Hi John,

I was searching for a way to deal with a Win 7 / Pdox 11 corrupt table when I saw this.  I have had two months of misery with a very stable program I wrote in Pdox 8 about 11 years ago. 

I can vouch for the problem and I'll be moving back to Ver 8 soon.  I loaded a software package that is written in Delphi (by a vendor) but uses the same BDE version that 11 uses.  Both programs have peacefully resided in the past but nearly the minute  I loaded the vendor software, my stuff blew up.  It didn't help that Corel loaded a program called pdxregcl.exe to wipe the Saved Paradox settings from the registry.  I have never had a corrupt database in this program and we use it daily in our business - until now. 

Problem is, I didn't know how to deal with it and the program wouldn't start because of the referential integrity links between master table and 5 child tables (which are only a few of the tables in the whole application), of which the corrupted was the money end of things.  I had to get it up overnight because we gave up most paper records because of the stability of the program.  I have all of the data to compare or copy out and add or object pal it into the repaired tables if I can get that far.

Now I'm not able to get the proper validity and referential integrity links back to being "whole" and we have had to use the software with the patched together table.  I had to disable the changeValue Event on the Customer.db - last name and phone (which are the primary key in these tables) because the child data gets lost on field depart, locks the database and requires Ctrl + Alt +Del to get out.

I'm still working at finding a solution but time is passing and I have a thousand or so recs to update since the last clean copies of data so I'm getting pretty desperate for anybody reading this who can help me out.

Regards - Bob

I, too, have experienced this problem with my installation of Paradox 11 (from WPO X5) on Windows 7. Everything seems to work fine except in two (quite important) circumstances:

First, as mentioned above, if I try to save a QBE in which the field order has been modified.

Second, when I work in SQL and run the SQL with the SQL query open (in edit mode), the query runs, produces an answer, and then gives the dreaded Paradox for Windows Desktop has stopped working. If I simply run the SQL without opening it for editing or viewing, it runs fine and does not effectively kick me out of Paradox.

Does anyone have a solution for this?

If not, does going back to an earlier version of Paradox work? What is the latest version that does work without problem?

Peter