This content has been marked as final. Show 6 replies
Thank you so much for your help!
We tried the import and have information about our tables, views, domains and sequences. We didn't get any information on table API including triggers nor did we get Entity information. Do you know what we need to do to import that information? Also, do you know what we can do to keep our Function Hierarchy Diagrams?
SQL Developer Data Modeler is no Designer.
There are two tools Oracle SQL Developer and Oracle SQL Developer Data Modeler. The triggers and packages are visible inside SQL Developer. They can be edited and enhanced with the tool. There is also an option to generate table api, but it might not be the code as generated from designer.
So check both tools, some things are better shown in Oracle SQL Developer Data Modeler and some inside Oracle SQL Developer.
If you generate your Forms from Designer, there just isn't an alternative.
Since there is no Designer 11g, you'll have to generate Forms 10g forms, and compile them with the 11g compiler. However, this doesn't give you the new Forms 11g features you may want to use. So, you need to do some post-generation editing in Forms Builder 11g if you want those features.
Our main reason for Designer is Forms generation. There are (plenty of) alternatives for entity and table modeling, API generation, writing pl/sql code etc., but none for Forms and Reports generation.
I'm not very familiar with Forms generation, or with later versions of Forms for that matter. How readable are the generated Forms? Is it feasible to leave Designer behind and start doing maintenance directly on the generated Forms, or is the generated code too hard to read?
I have used mostly the Web PL/SQL generator, and I can say that the generated PL/SQL is pretty hard to read and understand. It would be possible to maintain the code without using Designer, but not pleasant at all. So I feel a bit stuck with Designer as long as I still need to maintain a system that was developed with Designer. However, all new pieces of my biggest Designer Web PL/SQL generator project were written with hand-coded PL/SQL or PL/SQL Server Pages.
There are a lot of case generated (CG$) trigger and procedures used in the Forms. For us the code seems to be very complex and hard to read.
But, also some of them seems to be never used or it is just the statement "null" in it.
We thought about SQL Developer Data Modeler to capture most of the Designer stuff. But still there is the technical documentation that is not fully supported by SDDM. Did anyone migrate these Designer documentation to an other tool? If yes, to which one and how? We tried the SDDM Report functionality to capture some of the documentation, but also these reports do not contain everything that Designer could provide.
There are also "Preference Sets" used in Designer and we are wondering how to migrate these to Forms Builder. Did anyone migrate these preference sets to Forms Builder in the past and has some experiences/examples/recommendations about that? We thought about one "global" form that could contain these preference sets and then inherit them.
There are also the Functional Hirarchie Diagrams in Designer, could they migrated to Forms or SDDM in any way? Or do we need to maintain these diagrams manually in a tool like Word or Visio?
If we could capture all the things mentioned above, we would like to continue just with Oracle Forms Builder 11gR2 in combination with other tools like SQL Developer and Data Modeler and if no other solution could be find out with some manual maintained documents.
For all recommendations and tips we are very interested and we would thank you all very much!