Redesign advice sought...

[straybullet]

Have a relatively simple database which was originally setup to produce a manager's manual (to assist in pricing out upgrades and color selection, etc)and printouts of choices made by customers.
Friday afternoon, the "powers that be" decided that not only will this database be used for its original purpose, it will now also be used to maintain customer choice pricing information. That in and of itself is not a problem except that as prices are to be updated quarterly, there will still be customers whose jobs are not yet complete. Naturally, the items they have previously selected should not have their prices updated.
Ex: customer 1234 has selected maple base cabinets @ $15 per linear foot. The price changes to $18 per linear foot. This change should only affect new customers and if customer 1234's record is pulled up, the old price should be shown.

How do I go about saving the information for the existing customer yet make the new information available for the new without duplication? Monday from work I can send a trimmed down version of the DB if anyone needs to actually see what Im dealing with here.

Let them hate - so long as they fear... Lucius Accius

 

[TheAceMan1]

How are ya straybullet . . . . .

Use the [blue]NewRecord[/blue] property to assign the latest price! (NewRecord is True, only for new records). In the AfterUpdate event of the control for [blue]maple base cabinets[/blue], something like:

[blue]   If Me.NewRecord Then
     Me!Price = [purple]LookUp Latest Price In Price Table[/purple]
   End If[/blue]

See Ya! . . . . . .