DB package using in Forms

Question

Hello!
We have migrate out application to other language.
To avoid hard coded sting using in Forms we move all the strings (from trigger, PU...) to package functions.
We estimate that it will be about 7000 functions in the package.
Does it can be some damage on application performance?
Thanks!

Answer 1

Oooooh! NOW I understand. By "other language", I was thinking another "computer" language, rather than spoken language.
I would create a table with maybe three columns: Message_ID, Language_code, and Message_Text. (Make sure you have unique key on Message_id, Language_Code.) And maybe a database package to go along. When the user logs in, you could determine what language to use, and store Language_code in a global variable, or in the database package (From Forms, you have to call a procedure in the package to set a package variable). The db package could also contain a Message_lookup function:
Function Msg_Lookup(Msg_id in varchar2) Return varchar2 is
  Msg  Varchar2(4000);
Begin
  Begin
    Select Message_Text into Msg
      From Messages
      Where Message_id = Msg_id
      And Language_code = Pkg_Language_code;
    Exception when no_data_found then
      Msg := 'Not found:  Msg_id='|| Msg_id ||', Lang='|| Pkg_Language_code;
  End;
  Return Msg;
End Msg_Lookup;Whenever any form needs to display a message, all you need to do is call the Msg_Lookup function:
Message( Language_Pkg.Msg_Lookup('ABC123') );With such a lookup table, you would not notice any slowness in your forms. You could even use the language table to set each item's Prompt_Text property when the form starts up.