Re: saving form 4.5

I can't imagine why it would work differently, unless maybe you have some System.Current_Form or
Get_Application_Property(current_form_name) calls someplace making it work differently. Or are you maybe connecting to a different user or database? Did you change both the fmb name as well as the module name?

Does your form set :System.Message_Level higher than zero? Do you have on-message or on-error triggers running? You may be missing some error messages.

HTH,
Steve Cosner
http://members.aol.com/stevec5088

In article <37EBCC14.E91E2AED_at_trw.com>, Leona Vo <leona.vo_at_trw.com> wrote:
>I have an orginal form called AEPOM that runs beatifully. I rename this
>form to AEPOM2, saved it, then run it (no changes made). Form AEPOM2
>behave differently, even though no changes were made from AEPOM other
>than renaming it.
>
>In AEPOM upon running, the first thing it did was go to the first block
>and execute the trigger KEY-ENTQRY. Thus, the form is in enter query
>mode. While AEPOM2 does not do this. So I forced enter query mode by
>creating the WHEN-NEW-FORM-INSTANCE with enter_query; command in this
>trigger. Sure when running AEPOM2 I'm in enter query mode, however, by
>doing this the form now only query one block at a time instead of the
>entire form all at once. In other words, upon running AEPOM2 I hit the
>query button at the first block, go to the second block and hit the
>query button again, then go to the third block and hit the query button
>yet again, etc, to query block one, two, three, .....
>
>Any ideas? I'm so stuck I need help. Thank you for any suggestion.
>
>Leona
>
Received on Sun Sep 26 1999 - 08:28:56 CEST