Re: forms 3.0 -> forms 4.0, automatic?

In article <2ojupr$lte_at_digdug.pencom.com> dae_at_pencom.com writes:  

> I have a client that is considering moving from primarily DOS client machines
> running sql*forms 3.0 apps, to MS Windows machines running sql*forms 4.0.

We have converted our Forms3 package to Forms4 (but not released it under Forms4 yet). The converter works, but leaves you with a character based interface which runs under a GUI manager. This is better than using a terminal emulator, but not much. You need to add GUI functionality after the event. We have had problems with losing characters from boilerplate, which seems to be associated with the default font size (try small fonts size 7 under MS Windows). We lost information in popup pages that were converted to windows - we had to alter the x/y and height/width parameters in some cases. Forms 4.0.11 had problems in generating certain forms in our application, but these have been fixed in 4.0.12. There is no easy way to generate multiple forms under Windows - we have had to do them one by one. The F3 to F4 converter does not convert V2 style triggers to PL/SQL (if you still have V2 style triggers). Watch out if you are using sqlplus scripts in silent mode - they are not silent anymore, even with plus31.

The strength of the Oracle tools is no doubt a matter of opinion, however I have found Forms3 to be an excellent development tool. If you will be operating on an Oracle database, Forms4 does seem to offer a lot of advantages in terms of transaction handling and basic database interactions. Having said that, I have seen Powerbuilder in use and was impressed. I believe an application written with an Oracle front end to an Oracle database will have a marketing advantage over an 'Oracle' application that used an alternative front end.

I would be interested in hearing from you when your decision is made.

-- 
Glenn Nicholas, Concept
Glenn_at_wplace.demon.co.uk