From: Info@KennedySoftware.ie   
      
   Dominick,   
      
   > There were two gentlemen here; they remind   
   > me of middle-agers, 50something, overweight, gray-haired, who think they   
   > know it all...   
      
   I belong to the same category (though not grossly overweight!) -   
   precisely 40 years working on Databases, Software, etc. Full-time.   
   Interestingly, in my experience, it's usually the young whipper-snappers   
   who are the "know-it-alls"... You recall that note on the side of the   
   fridge, from the Parents to the 20-somethings - "Move out, get yourself   
   an apartment, fend for yourself - while you still know everything!".   
      
   And, if YOU're not yet in that category, then, with luck, you're headed   
   that way!   
      
    > ...who claimed that I was trying to cheat my way into a position,   
   > when all I'm trying to do is get familiar enough with paradox so that I can   
   > speak intelligently during a possible interview.   
      
   You're splitting words here, Dominick. They all add up to the same   
   thing; check your thesaurus - bluff, waffle, cheat, "speak   
   intelligently", bullsh**, imposter, etc, etc...   
      
   And, if you get past this interview, then what? Paradox (Win or DOS), in   
   many respects, is more powerful than Access, and will you then be able   
   to unravel precisely what the Paradox app is doing, and will you be able   
   to implement such features in Access? What might the employer end up with?   
      
    > The client needs to migrate   
   > paradox into an Access database, that's all and I know Access, but not   
   paradox.   
      
   If you review posts here over the years, you'll see many comments   
   suggesting that moving from Paradox to Access is the equivalent of a   
   "downgrade".   
      
   > BTW, do you think there is documentation, out there, that shows a typical   
   > Paradox database structure?   
      
   The normal documentation with Paradox is excellent, and, obviously, will   
   cover all your queries. And there are some 3rd party books on Paradox   
   also. Maybe Amazon, etc. Apart from garnering enough info for that   
   interview, you'll be able to concentrate on the aspects that suit your   
   own current DB knowledge/experiences, and you may also be able to decide   
   if the project is doable anyway - by you, or, indeed, by anybody!   
      
   As a general point, if you're familiar with numerous Database systems,   
   eg, Oracle, Sybase, MySQL, MS-SQL, PostgreSQL, DB2, etc, etc, (but not   
   Paradox), then you'll have no major problems getting a good handle on   
   Paradox, including the OPAL/PAL languages. If you know ONLY Access, and   
   especially if the Paradox app is a complex one, maybe you should   
   re-think your interview strategy at this time - the task might be very   
   complex. And, if I were the employer, I might not be impressed, and I   
   might make my views known generally...   
      
      - Mike   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)