迁移基于字符的Oracle表单 [英] Migrating a Character Based Oracle Form
问题描述
我有一台运行DG/UX的旧服务器，不久之后将不再支持该服务器.我有一些基于字符的oracle表单，需要从这台机器上迁移出来.有谁知道Oralce为升级这些基于字符的报告采取了什么样的迁移策略.它不一定必须是最新版本，甚至不必是GUI版本，但是我确实需要迁移到受支持的OS(例如linux).
I have an OLD server running DG/UX that will in the near future be unsupported. I have some character based oracle forms that need to be migrated off of this machine. Does anyone know what sort of migration strategy Oralce has for upgrading these Character Based reports. It doesnt have to be the newest version, it doesnt even have to be to a GUI version, but I do need to migrate to a supported OS such as linux.
推荐答案
The easy answer is to tell you to check out Migration from 6i to 10g.
以前，我认为更有用的答案是告诉您从头开始重写那些表格和报告.可能是在另一种工具中-特别是如果您希望具有Web界面等，而不是被古老的Java运行时所困扰.
Having done it before, what I think the much more useful answer is to tell you to rewrite those forms and reports from scratch. Probably in another tool - especially if you want to have a web interface, etc. rather than being hobbled by an ancient Java runtime.
有一些产品可以让您将旧表单代码转换为PL/SQL. Kumaran 就是一个例子，但是我发现它有故障，不得不做很多事情编辑代码以使其与原始代码相同.
There are products out there that will let you translate the old forms code into PL/SQL. Kumaran is an example of one, but I found it buggy and had to do a lot of hand editing of the code to get it work the same as the original.
就我而言，CUI已死，因此您最好还是一直使用GUI.我上次查看该文档时，几乎没有关于CUI表单的文档，并且在GUI中起作用的东西经常根本无法在CUI中起作用.
As far as I'm concerned, the CUI is dead so you might as well go all the way to a GUI. The last time I was looking at it, there was almost no documentation for CUI forms and frequently things that worked in the GUI wouldn't work in the CUI at all.
在将基于CUI的表单应用程序转换为GUI时，您可能会遇到一些问题.
There are some problems you may run into in converting CUI based forms applications to GUI.
-
有时，当用户移至下一个或上一个字段/块/等时，会进行验证和特殊处理.当您切换到适当的GUI时，您的用户只需单击另一个字段即可跳过这些事件.因此，您有两个选择-#1审核所有表单，或#2禁用鼠标的表单导航
Sometimes there is validation and special processing done when the user moves to the next or previous field/block/etc. When you switch over to a proper GUI, your user can skip those events by just clicking on another field. So you are left with two choices - #1 audit all of the forms or #2 disable navigation in the form with the mouse
选项1的工作量少于重新开发的工作量，但请看我们已经投入了多少工作量.
Option #1 is less work than redeveloping but look at how much work we've already put into it.
选项2，您的用户会讨厌您，并且会用音叉和火把追赶您.他们会意识到，您投入其中的所有工作都没有任何价值.然后您最终还是会执行选项1.
Option #2 your users will HATE you and come after you with pitch forks and torches. They will perceive that they've got nothing of value for all the work you put into it. Then you will end up doing Option #1 anyway.
有时，在CUI中可以正常工作(或受其限制而需要)的UI完全是错误的，并且打破了用户习惯于在GUI的其余部分中使用的UI隐喻(例如，弹出列表的列表，您必须在其中选择一个条目，而不是在下拉列表中直接选择正确的值)
Sometimes a UI that works fine in (or is required by the limitations of) a CUI is just plain wrong and breaks the UI metaphor that users are used to working with in the rest of the GUI (e.g., a pop-up window with list that you have to select an entry in rather than pull down where you can just pick the right value directly)
当转换为GUI时，CUI可能会具有与新编写的表单不同的字体，文本大小和其他格式默认值(对我而言是这样).因此，现在要么必须更新整个表单集，以遵循Oracle表单/报表的新默认主题，要么每个新表单/报表都必须还原为以前的旧笨拙样式-否则它会像拇指一样伸出来(您的用户将希望他们现在都像漂亮的一样).
When converted to a GUI the CUI may end up with different fonts, text sizes and other formatting defaults than a freshly written form (it did for me). So now either the whole set of forms has to be updated to follow Oracle's new default theme for forms/reports or every new form/report has to reverted back to the old clunky style you had before - or it will stick out like a sore thumb (and your users will want them all to be like the pretty one now).
不是您想要的答案；嗯但是您可以以此为借口摆脱Forms/Reports升级步伐，甚至可以清除多年来必须发生的一些黑客攻击.
Not the answer you wanted; huh. But you can use this as an excuse to get out of the Forms/Reports upgrade tread mill and maybe even clean up some of the hacks that have had to happen over the years.
这篇关于迁移基于字符的Oracle表单的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
