| Forms 4.5 vs. 10g [message #128581] |
Tue, 19 July 2005 10:04  |
mariaschreiber
Messages: 11
Registered: June 2005
|
Junior Member |
|
|
Hy List,
simple question has ever one off you seen an Forms 4.5 Application
Runing against Oracle 10g is there some thing special to Configure
NET 8 / SQL NET
Thanx Maria
|
|
|
|
|
|
|
|
| Re: Forms 4.5 vs. 10g [message #331464 is a reply to message #128581] |
Thu, 03 July 2008 08:34  |
rysiekmus
Messages: 3
Registered: May 2007
Location: UK Manchester
|
Junior Member |
|
|
Hello All,
I have a similar problem, but due to hardware limitations I would like to run my Forms45 binaries in a 64-bit AIX environment. We are planning to upgrade the applications for the web based Forms, but we need a grace period to install Oracle10g on all servers, so we will switch the AIX from 32bit mode to 64bit mode.
Will forms45 run on a 64bit machine?
Thanks in advance.
Richard
|
|
|
|
|
|
|
|
|
|
| Re: Forms 4.5 vs. 10g [message #508495 is a reply to message #508484] |
Sun, 22 May 2011 02:41 |
 |
Littlefoot
Messages: 21818
Registered: June 2005
Location: Croatia, Europe
|
Senior Member
Account Moderator |
|
|
I hope that your problems are raised in test environment (and not production one).
I suppose that you should have migrated application from Forms 4.5 to 6i first (which shouldn't be a problem - simple COMPILE would do the job) (migration to Forms 10g seems to be a more complicated task, if you ever plan to do it). Anyway, how come you didn't consider upgrading your application along with the database? Now you have a HUGE step between.
As these procedures are stored procedures, check whether all required privileges are granted to a user that is compiling those forms. Furthermore, while Googling around, I found a note where someone said that there was a problem with a stored procedures' length (meaning "number of lines"); 5000 was a limit, and none of the "longer" procedures was recognized by Forms 4.5. Their workaround was to create another stored procedure that only called that "lengthy" procedure, and make changes in Forms calling those "new" procedures first. Something like this:-- a new stored procedure
create or replace procedure new_prc_employee is
begin
prc_employee; -- this is existing, loooong procedure
end;
-- Forms trigger
<some_code_here>
-- prc_employee; -- comment this line, as it calls a long procedure
new_prc_employee; -- and call a new procedure instead
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
