Effects? changing of package specification in .pll

Question

dear all,
Have you experience the following problem:
I have a library attached to several forms. these form share some context data in this library (i always use call_form with share_library_data option). I add a procedure to one package in the library mentioned and attach it to a new form. This form and the old forms couldn't share the context data in the library.
I solve it problem by delete the attachment in all the old form, reattach the library and compile all the forms. Since I have a great number of the old forms, it is not pratical thing to do.
Is it the only way to do it ? or is there any elegant solution ?
what happens here?
Please help
null,

Answer 1

Look at it from the database's perspective: Forms has a where clause that it sends to the database that contains a reference to a package variable that reside on the client. What can the database do with that? It knows nothing about client side package variables. How would it discover and substitute that reference with the value of the client's package variable?
Now look at it from Forms' perspective: you have declared a where clause that you know contains a reference to a package variable. How will Forms know to substitute the reference for the actual value? With Forms items you use the semicolon notation but for package variables there is no analog.
You need make the full where clause yourself including substituting the reference for the the actual value. The way to do that is with set_block_property and the DEFAULT_WHERE.
From the help file:
"DEFAULT_WHERE sets the WHERE clause on the block and OVERRIDES the value set at design time.
The WHERE reserved word is optional. The default WHERE clause can include references to global variables, form parameters, system parameters, and item values, specified with standard bind variable syntax."