BOster
Legendary Poster
<Editorial Mode Begin>
I like Powerforms and what they allow you to do and build, but I swear they are quite possibly the buggiest and most inconsistent development tool I have ever worked with.
<Editorial Mode End>
This power edit form has me on the ledge, please, someone talk me down.
I have a VERY simple APPL to edit a table. For the sake of my problem lets say the table has five fields:
*BranchPlant
*ItemNumber
*Lot
*SalesOffice
Quantity
*Key fields
The Power Edit form has the first three fields as header Fields (FC). These serve as data entry and filter fields. When editing records they must contain values. The last two fields are in a grid. To summarize:
FC_BranchPlant
FC_ItemNumber
FC_Lot
----------
GC_SalesOffice
GC_Quantity
In EDIT_MODE the user can add, edit, delete records w/o any problems. In ADD_MODE the user can also add records w/o any problems. In both cases it uses the values entered in the FC variables when writing multiple records to the table. However, if I pass values in the FI variables and assign to the FC variables during dialog initialization as in:
FC_BranchPlant = FI_BranchPlant
FC_ItemNumber = FI_ItemNumber
FC_Lot = FI_Lot
ADD_MODE stops working, as in it wont add any records to the table. No errors, or anything just closes the form and returns to the calling form like nothing happened... which is exactly what happens... nothing.
I have tried too many things to count. Here are some of the things I remember having tried:
1. Set BC_xxxx = FC_xxxxx in various events like the Form's "Add Record To DB..." event(s) and various Grid events.
2. Assigning the FC_xxxxx = FI_xxxxx in various form initialization events (Dialog Init and Post init).
3. Creating additional form interconnect params that are not directly connected to the BV and then assigning the FC values from those. Thought for sure this would work. Nope.
4. Exactly 1 billion other things.
Basically it seems like as soon as I touch the FC variables in either the "Dialog Intialized" or "Post Dialog Init" events, ADD_MODE quits working (BTW, also tried assigning BC values in these form events as well). Just as a test I even hard coded values into the FC variables instead of using FI variables in the "Post Dialog Init" and it still breaks ADD_MODE. One very weird thing I noticed. In the debugger, the grid's "Add Grid Rec to DB" is not firing (neither is the "Update Grid Rec..." event). Litterally, as soon as I assign a value to an FC variable it doesnt even attempt a table insert or update.
I know I am probably missing something silly and I feel rediculous for having to ask this question, but I'm about ready to recreate the printer scene from the movie Office Space with my PC assuming the role of "printer". I am sure someone can tall me what little check box I forgot to check or property that needs to be set, etc.
I like Powerforms and what they allow you to do and build, but I swear they are quite possibly the buggiest and most inconsistent development tool I have ever worked with.
<Editorial Mode End>
This power edit form has me on the ledge, please, someone talk me down.
I have a VERY simple APPL to edit a table. For the sake of my problem lets say the table has five fields:
*BranchPlant
*ItemNumber
*Lot
*SalesOffice
Quantity
*Key fields
The Power Edit form has the first three fields as header Fields (FC). These serve as data entry and filter fields. When editing records they must contain values. The last two fields are in a grid. To summarize:
FC_BranchPlant
FC_ItemNumber
FC_Lot
----------
GC_SalesOffice
GC_Quantity
In EDIT_MODE the user can add, edit, delete records w/o any problems. In ADD_MODE the user can also add records w/o any problems. In both cases it uses the values entered in the FC variables when writing multiple records to the table. However, if I pass values in the FI variables and assign to the FC variables during dialog initialization as in:
FC_BranchPlant = FI_BranchPlant
FC_ItemNumber = FI_ItemNumber
FC_Lot = FI_Lot
ADD_MODE stops working, as in it wont add any records to the table. No errors, or anything just closes the form and returns to the calling form like nothing happened... which is exactly what happens... nothing.
I have tried too many things to count. Here are some of the things I remember having tried:
1. Set BC_xxxx = FC_xxxxx in various events like the Form's "Add Record To DB..." event(s) and various Grid events.
2. Assigning the FC_xxxxx = FI_xxxxx in various form initialization events (Dialog Init and Post init).
3. Creating additional form interconnect params that are not directly connected to the BV and then assigning the FC values from those. Thought for sure this would work. Nope.
4. Exactly 1 billion other things.
Basically it seems like as soon as I touch the FC variables in either the "Dialog Intialized" or "Post Dialog Init" events, ADD_MODE quits working (BTW, also tried assigning BC values in these form events as well). Just as a test I even hard coded values into the FC variables instead of using FI variables in the "Post Dialog Init" and it still breaks ADD_MODE. One very weird thing I noticed. In the debugger, the grid's "Add Grid Rec to DB" is not firing (neither is the "Update Grid Rec..." event). Litterally, as soon as I assign a value to an FC variable it doesnt even attempt a table insert or update.
I know I am probably missing something silly and I feel rediculous for having to ask this question, but I'm about ready to recreate the printer scene from the movie Office Space with my PC assuming the role of "printer". I am sure someone can tall me what little check box I forgot to check or property that needs to be set, etc.