From: contactATharganonlineDOTcom@nospam.net   
      
   Hi,   
      
   I thought I'd share my experiences, in case they were relevant. When I used   
   Pdox 8, opening a table with a broken Lookup link would *always* GPV, and   
   there was *no* way to fix it. The broken link *had* to be repaired before   
   the table could be opened, or even repaired. This meant reconstructing --   
   which Paradox hardcodes into the table structure when it creates the link.   
      
   Now I use Pdox 11.0.0.411, and tables fail gracefully when they have a   
   broken lookup link. They throw up an error which gives the user the chance   
   to sever the link; when this is chosen, the table opens normally and   
   without GPV. (Pdox 8 threw up the same error box, but would GPV before the   
   table could be fixed or opened.)   
      
   The gurus around here advise that you handroll your own lookup to prevent   
   this problem. Bear in mind that the *actual path* is hardcoded, not the   
   alias. So if you install your app on a client computer, you must duplicate   
   this path exactly (including the drive letter IIRC.) Same goes for the   
   built-in referential integrity.   
      
   If you use Pdox as a personal workstation database, as I do, the built-in   
   lookup is too tempting to resist. For my money, it is useable *only* on   
   versions late enough to allow it to fail gracefully -- evidently only Pdox   
   11.   
      
   Now, as to recovering data: Try to reconstruct the exact path structure   
   present when the lookup was created, from drive letter to file name. That   
   should let you repair, then restructure, the table.   
      
      
   Jim Hargan   
      
   On 20 Nov 2006 06:42:48 -0800, Fred Z wrote:   
      
   > Does anyone have a solution for the GPV that comes when the Table   
   > Lookup tab is pressed in the Table Create, Restructure and Info   
   > Structure dialogs? My Paradox 10.0.0.990 installation started doing   
   > this yesterday after letting me look at and alter Table Lookups for   
   > years.   
   >   
   > The other machines on our office network can still restructure Table   
   > Lookups across the network.   
   >   
   > Yesterday I had a GPV during a scan in which I was changing a large   
   > table. The target table, which was newly created and started empty got   
   > so corrupted that the table repair utility wouldn't fix it and failed   
   > itself. I guess this damaged the registry somehow.   
   >   
   > Other people with the same problem have suggested a re-installation   
   > does not work.   
   >   
   > Any ideas, short of a disk reformat?   
   >   
   > Fred Z   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)