I want to find a solution for Forms 6i 220.127.116.11.2 on Windows 7 (32 Bit). We get the follwoing errors, if we want to use Reports-Server:
DBMS Errorcode: 1403 and Errtext: ORA-01403
By the way, we can use Reports-Server on Windows 7 (64 Bit) after change NN60.dll und NNB60.dll with older version of DLLs.
Is there any experince regarding this matter?
Thanks in advance,
Are you aware that Forms/Reports 6 was desupported years ago, long before Windows 7 even had a name? Is there are particular reason why you are using this almost 15 year old product with a near new operating system? Why not use a current version like 18.104.22.168 assuming you are licensed to do so?
If you really want Forms/Reports 6i to work in a Win7 environment, good luck. Your best chance for success will be to use "Windows XP Mode" which is basically a virtualized WinXP environment running in Win7. It is free to licensed Win7 Professional or higher owners. It is not supported (as far as I know) with Win7 Home Ed.
Thanks for your reply. In this case, unfortunately, we "have to" find a solution. In addition, I'm not sure, if Oracle has a solution for "old" Applikation such as Forms 6i.
If it's possible, can you provide me feedback regarding this matter, please? or some docs regarding migration from 6i to 11R2?
Thanks in advance,
Although it's not certified I am running a forms 6i application on win7 64bit. So far nothing too hard (in fact as I installed developer suite it was easier to install then the 10g version...); the only thing I did was to apply the latest patchset for forms 6i (22.214.171.124.0); both forms and reports are running fine (I am using reports almost never though). This doesn't mean this should always work, but at least you have a little chance to get it working. As for your ORA-1403: did you try to debug your report?
would indicate a problem in your code to me, not a OS problem...
You should look into upgrading though; here's a starter:
Thanks a lot for your reply. As you wrote, on Win7 64bit works, but my question is, if one solution for Win7 32bit is available.
I'm agree with you, but at this moment, I consider this error as side-effect for main error. But I'll check again...