I haven't had the chance to tinker with this problem, but I have an idea that I'll hope to try this weekend. I plan to remove all keys, then copy the .DB files only to a fresh install of Paradox on another computer, and rebuild the indexes there. If that works and the lookup tables error disappears, I'll wipe out all traces of Paradox from the first computer, reinstall it, and try the same thing in reverse.
My only hesitation is that I'd have to print all the table structures in order to remember all relationships and indexes before starting this. That may take some time.
I get the newsfeeds from Corel.Paradox and there are a couple of current threads on table lookups, someone suggesting that some of the Paradox code pre dates Win95 and dates back to the old DOS engine. The important thing that comes out of this is the file name and unaliased directory paths need to adhere to old 8.2 conventions and directory path character length limitations which (head above the parapet ! ) are 256 chars long. Correct me if I'm wrong on these details. Having said that, I am running Paradox 9 under XP pro on two machines at present and they have long non-DOS type directories and the table look ups still work ( touch wood ! ). Ihave had problems in the past but after clean installs the problem dissappeared.
Reading through this and contemplating some of the ideas I have received from other forums, I am sorely tempted to see if I cann find my copy of Paradox 9, install that, and see what happens.
Having tried Paradox 11 on Win Vista I encountered many problems (but non of the issues discussed at the time) the main problem was with lookup tables. In order to work I had to remove the lookups and remake (similar to the transition from Pdox 16 bit to 32 bit). I was also unable to use a lookup from a different directory (I have one database supplying lookup values to many of my others - a "Paradox Database"). I installed Wni XP on a virtual machine but still with Pdox 11. The lookup problems remained.
My "solution" was to re-install Pdox 9. This solved all lookup problems. This also returned portability between non networked computers. It may not be elegant but it works.
Elsewhere in this forum there was a recommendation to revert to Pdox 9 for other reasons.
(Note; I am not an expert nor a programmer, just a long-time user).
I think you are very brave. The more I research this issue, the more I think there to be a weakness, (not the same thing as a bug) in that I tried a brand new installation on a new computer and the lookup function was available to me. Within a very short time, I lost it again. I think the problem is related to some kind of leakage with the combination of Paradox 11.0.0.411 and XP sp3.
I have tried to discover (without success) whether or not the version of Paradox in X5 is free of this issue, but have so far not asked the right people. That is, I don't have an answer yet.
"I think the problem is related to some kind of leakage with the combination of Paradox 11.0.0.411 and XP sp3"
I was using Vista when this problem first cropped up, and upgraded to Win 7 where it still remained a problem. As far as I know, Paradox X5 = Paradox X3 = Paradox 11. There hasn't been an upgrade in years.
OK, I may have stumbled across the solution to the Table Lookup problem described here, purely by accident. As Cottage Builder writes:
"In table restructure, the 'lookup dialogue box' is not available. When I
attempt to invoke it, the program returns the error message;.....
Access Violation at address 00A8F6AC in Module 'PXDCRT32.DLL' . read of address 00000000."
In attempting to solve another problem, the dreaded "retain settings and don't show the Welcome Screen on startup" issue, I followed these directions to delete the Registry Cleaner files (found elsewhere on this board):
d:\Program Files\Paradox\Programs\PdxRegCl.exe
d:\Program Files\Paradox\Programs\PdxRegCl.ini
I also removed the registry entry for pdxregcl.exe from: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Now, maybe I did something wrong, but when I restarted Paradox, the Install box came up and asked for me to insert my installation CD. I did, and the two PdxRegCl.* files were re-installed.
Yet, somehow, both the retain settings issue and the Table Lookup issue seem to have been resolved by this sequence of events. I can now open the Table Lookup tab of any database without the Access Violation message, and even though the Registry Cleaner files appear to have been reinstalled (but removed from the Run directory of the Registry), Paradox has stopped showing the Welcome Screen and recalls my settings from my last exit.
Cottage Builder, maybe you can try this and see if it works for you?
What I discovered was that the reason for that crash, in my XP SP3 pc, was the presence of a webcam in my system that put an icon in my computer resources.
I used ShellExView to disable the scanners and cameras shell folder extension, and the table lookup page returned to regular operation, both on Pdox10 and Pdox11!
Frelance IT consultant and programmer since 1991: www.atipica.it
Wow, that's strange. I take it you can duplicate the problem/solutions so that if you enable the scanners and cameras shell folder extension, the problem returns. That's an interesting conflict.
Sure I can! In fact, simply disconnecting the webcam from the usb port solved the problem, and reconnecting it made it reappear!
By using shellExtView I managed to keep the webcam connected (and functional in programs such as Skype) but not listed in My computer, and that made Pdox work correctly even when the webcam is connected...
Surely it's a strange thing, but not too much if you consider that the Table Lookup tab has a folder chooser field on it, and that field has a drop down box that get populated with what you have in your My computer folder... :)
Frelance IT consultant and programmer since 1991: www.atipica.it
Paradox
Print This
