Re: Developer 2000 weak points??

Jerry Gillard <DoubleEx_at_prolog.net> writes:  

>We're considering Developer 2000 for our development tool working with Oracle Databases. Some of my associates
>are not overly excited about Oracle tools because of their weak track record in this area. However, I think
>Oracle may have a good product here but am not hearing much about it.
>
>From those of you who use it, is it reasonably fast and usable when deployed (not developed) on 8mb pcs? Are
>there any downsides you could throw at me since Oracle has shown me the shiny side?
 

Don't just read the "feature" sheets.  

Actually try the Oracle Forms development environment, and develop a prototype.  

Also try one or more other development environments; one that provides many of the application capabilities that Forms provides is Microsoft Access. A more 3GL/less 4GL environment is Microsoft's Visual Basic.  

You will likely find the development environment for Oracle Forms to be SIGNIFICANTLY more cumbersome than either of the Microsoft Products. You will also need more RAM memory for the Oracle development environment to avoid constant page-faulting to and from disk. (I hear Microsoft Access 95 is getting large, and 16 MB is recommended for development. However, 24 to 32 MB is recommended for Oracle Forms development. Access needs 12 to 16 MB for run-time, and Oracle Forms really needs 16 MB for run-time. Visual Basic needs much less memory for both development and run-time, but provides less "free" functionality compared to both Forms and Access.)  

Also run PowerBuilder and see if you like its development and run-time "feel".  

Again, DON'T just read the "feature sheets"!  

• Rick --

(Rick Rutt is a system architect living and working in Midland, Michigan.) Received on Thu Apr 18 1996 - 00:00:00 CEST