From: jeffshoaf@alltel.net   
      
   I've had that happen when a user opened a report directly using the full   
   version of Paradox w/o having the correct working directory set (or   
   appropriate alias set up). Paradox displays an error message, then, when   
   the user closes the report, displays another message saying the report   
   has changed and asks if it should be saved. If the user saves it, the   
   next time the report is opened, it'll be missing it's datamodel.   
      
   That's a good argument for providing delivered reports to users and/or   
   restricting them to using Paradox Runtime.   
      
   Anne Wainwright wrote:   
   > Hi,   
   >   
   > Solved that. All the fields were undefined, but how they got like that   
   > beats me. Found an earlier backup and that worked fine.   
   >   
   > Anne   
   >   
   > Anne Wainwright  wrote in   
   > news:Xns98BE9206EC4F3azopane@196.25.240.158:   
   >   
   >> Hi there,   
   >>   
   >> My annual dose of paradox has arrived. Happy 2007 to all.   
   >>   
   >> Pdox9 for the record.   
   >>   
   >> i have a report that I run on one table, using the filter as needed.   
   >>   
   >> Yesterday it was fine   
   >>   
   >> Today the filter button is greyed out in the report design mode. I   
   >> restored an earlier copy with no improvement so I imagine it is some   
   >> setting somewhere. I can find nothing. The table was not changed,   
   >> everything else runs fine.   
   >>   
   >> What simple thing have I overlooked?   
   >>   
   >   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)