I tried searching but haven't found a similiar circumstance yet so I'm hoping someone can help me.
I had an earlier problem with my posting rules but got that all figured out.
I have a table which summarized all my new equipment info. In this table are two posted fields which come from another table called dates. This table has the activation date and memo field as well as a removal date and memo field.
When I create a new equipment # based on following set. This set includes parent table NRT_No (creates sequential #), child table Master_Eqmt (new equipment info) and grandchild table NRT_dates (activation and removal dates). All tables are linked by Inv_No.
When I use the form created by above set, I enter the activation date and it posts from date table to eqmt table and everything is ok. I would continue to use this set for my removal form but my Inv_No field in my date table is a lookup to Master_Eqmt does not work at the child or grandchild level.
I created another set in which NRT_dates is the parent and Master_eqmt is the child. My lookup works and I choose a piece of eqmt that I want to remove. It displays the eqmt on my form including the activation date and was entered prior. This form only allows you to enter removal date. When it posts, the activation date and memo fields in my Master_eqmt table disappear and only the removal date and memo fields show up on the table.
I have tried using prevent changes etc in the set rules but nothing seems to keep my original date entry intact in the table.
I don't understand why this happens? When I look in my date table both entries (activation and removal dates) are there. The values in these fields are posted to my Master_eqmt table so I wouldn't think being on separate lines in the date table would matter. But everytime I enter a removal date my activation date disappears from my eqmt table.
Help!!! :0)
Thanks Sue
I had an earlier problem with my posting rules but got that all figured out.
I have a table which summarized all my new equipment info. In this table are two posted fields which come from another table called dates. This table has the activation date and memo field as well as a removal date and memo field.
When I create a new equipment # based on following set. This set includes parent table NRT_No (creates sequential #), child table Master_Eqmt (new equipment info) and grandchild table NRT_dates (activation and removal dates). All tables are linked by Inv_No.
When I use the form created by above set, I enter the activation date and it posts from date table to eqmt table and everything is ok. I would continue to use this set for my removal form but my Inv_No field in my date table is a lookup to Master_Eqmt does not work at the child or grandchild level.
I created another set in which NRT_dates is the parent and Master_eqmt is the child. My lookup works and I choose a piece of eqmt that I want to remove. It displays the eqmt on my form including the activation date and was entered prior. This form only allows you to enter removal date. When it posts, the activation date and memo fields in my Master_eqmt table disappear and only the removal date and memo fields show up on the table.
I have tried using prevent changes etc in the set rules but nothing seems to keep my original date entry intact in the table.
I don't understand why this happens? When I look in my date table both entries (activation and removal dates) are there. The values in these fields are posted to my Master_eqmt table so I wouldn't think being on separate lines in the date table would matter. But everytime I enter a removal date my activation date disappears from my eqmt table.
Help!!! :0)
Thanks Sue
Comment