From: CDB4W@NOSPAM.bigpond.com   
      
   "Leslie Milburn" wrote:   
      
   >   
   > BUT, in some projects that will not be enough. I have worked on projects   
   > especially older ones where data *not* being present meant something. In   
   > order to know under which scenarios data would not be present required   
   > access to the business rules. To read the business rules in P4W would   
   > require navigational knowledge in order to locate the code in the first   
   > place (Not usually centrally located in older apps), and then you would   
   > need to be fairly proficient in OPAL to then read the code etc.   
   >   
      
   Having said all of that......   
      
   If it was my main application we are talking about then the requirements   
   would again be different given that I no longer use the P4W application. So   
   in my case, the applicant would need to know C programming to be able to   
   understand the Database Business Rules of which there are a couple of   
   hundred thousand lines of code handling that aspect alone. Also from a   
   reporting aspect they would need Crystal Reports Knowledge because again   
   there are Report generation rules within that side of things as well. Of   
   course lets not forget that Delphi/BDE is probably the most likely candidate   
   after P4W and so thats another one thrown into the mix.   
      
   So this is what I mean when I differentiate between data transfer and   
   something more than that. This is why we here differentiate between a   
   Paradox Database and Paradox the Application.   
      
   I mean we are not talking about passing an exam here we are talking about   
   data that is most likely business critical (otherwise why bother) and   
   mistakes would be costly. So, you either have the required skills or not. If   
   you do then great and if you don't then thats life - move on.   
      
   Leslie.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)