calculated records

[paulevans]

Hi

I have read a number of these threads now where it says you should not generate new records based on calculated fields. So can some one help with my following problem.

I am creating a customer/contract database where when an order is created, a record set is generated to store dates for invoice periods. I have done this by using the start date of the contract and then adding onto this a value of x days that updates a table giving y records based until the end date of the contract.

Is this the best way to do this or can some one tell me a better way.
Thanks

 

[RuralGuy]

You may be refering to the threads that state that except for certain conditions, it is almost always a lousy idea to store calculated values. It is difficult to say for certain but as you describe it, I see nothing wrong with your approach to the problem. Someone else may have a different view.

 

[neileg]

You might argue that a more elegant approach would be to test each day to see if it has been x days since the last invoice. If the answer is yes, you create a new invoice.

I'm not keen on generating tables of empty records. However, I'm also pragmatic and agree with RG that sometimes it's easier to do whatever works for you.

 

[paulevans]

Thnaks guys
This is what I was thinking.
What is causing me a problem now is how this works as a relationship.

I have a table contract setup and another one called valuation. from calculating the dates my valuation table is updated with the new dates but I do not seem to beable to reference these from a master form which is based on the contract setup table I then have a subform which I want to show the dates in. when I add a new record in my contact set up and generate new dates for this table they do update in the sub form. However when I move to record set one of contract form all dates are displayed from record one of the valuation record.

 

[RuralGuy]

It sounds like your LinkChild/MasterFields are not set up properly.