Hi Everyone,I am in desperate need of some assistance from the experts here. I'm working on a project to convert an existing application from Oracle 8.1.7 to DB2 9.7 on windows. The application has a MS Access 2000 front end. The current implementation on Oracle works fine.
Here is the issue I am coming across with DB2:I have a main form named "frmItemUpdate" that has a query for a recordset which retrieves data from table a. There is a subform named "subFrmItemRequiredData" on the main form which also has a query for a recordset which goes against the same table as the main form. One of my modules issues the following command:
DoCmd.OpenForm "frmItemUpdate",,,,acFormAdd
From what I understand, this command is suppose to open the form to a new blank record. When I debug this using the Oracle backend, the Form_Load event of the subform is the first event to occur after the command above is executed. When I debug using the DB2 backend. the first event to occur is the Form_Open event on the main form. If I remove the acFormAdd argument, it behaves just like the Oracle implementation by going to the Form_Load event of the subform. For the life of me I can't figure out why the DB2 implementation is behaving differently when the acFormAdd argument is used. The table both queries are executing against has a primary key defined. Can someone explain to me what exactly the acFormAdd argument is doing to the underlying table involved in the query? Is it trying to insert a blank row in the underlying table? Is this a limitation in regards to using DB2 linked tables compared to Oracle? Any help would be appreciated. I have spent several days trying to figure this out and feel like I haven't made any progress.Thanks
Here is the issue I am coming across with DB2:I have a main form named "frmItemUpdate" that has a query for a recordset which retrieves data from table a. There is a subform named "subFrmItemRequiredData" on the main form which also has a query for a recordset which goes against the same table as the main form. One of my modules issues the following command:
DoCmd.OpenForm "frmItemUpdate",,,,acFormAdd
From what I understand, this command is suppose to open the form to a new blank record. When I debug this using the Oracle backend, the Form_Load event of the subform is the first event to occur after the command above is executed. When I debug using the DB2 backend. the first event to occur is the Form_Open event on the main form. If I remove the acFormAdd argument, it behaves just like the Oracle implementation by going to the Form_Load event of the subform. For the life of me I can't figure out why the DB2 implementation is behaving differently when the acFormAdd argument is used. The table both queries are executing against has a primary key defined. Can someone explain to me what exactly the acFormAdd argument is doing to the underlying table involved in the query? Is it trying to insert a blank row in the underlying table? Is this a limitation in regards to using DB2 linked tables compared to Oracle? Any help would be appreciated. I have spent several days trying to figure this out and feel like I haven't made any progress.Thanks