From: dominickdimantova@comcast.net   
      
   Well, I may be asked to migrate paradox database objects into an Access   
   database   
   and I just want a brief overview of the paradox database, so that, in a   
   possible   
   interview, at least I can say something intelligent about paradox that would   
   enhance my chances, with my Access background, for getting this contract   
   assignment.   
      
      
      
      
   "Larry DiGiovanni"  wrote:   
   >Dominick DiMantova wrote:   
   >   
   >> Hello, I would like to know if I can get an overview of a paradox database   
   >> structure and architecture?   
   >   
   >I assume you mean Paradox application structure and architecture, e.g.,   
   what   
   >are typically the various pieces of a typical Paradox app, how do they fit   
   >together, and how do you begin to digest such a thing.   
   >   
   >If that's the case, then it matters to ask, DOS or Windows?  Very different   
   >beasts.   
   >   
   >Steve has a point in that a little knowledge can be a dangerous thing.   
   Be   
   >advised that poorly documented, poorly structured, poorly conceived Paradox   
   >apps are very common, typically consisting of hundreds of tables and   
   >development artifacts (many unused, the result of ad hoc analysis or aborted   
   >development) with little rhyme or reason, or worse - dumped into a single   
   >directory.  Going in to something like that with little or no experience   
   in   
   >this is often less desirable than a few extra months' unemployment.  :-)   
   >   
   >Out of curiosity, what is the migration target platform/language?   
   >   
   >--   
   >Larry DiGiovanni   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)