Temporary record changes...

[jetson]

My database is for flower arrangements. So I have a master record for the arrangement and related records for all of the pieces that go into an arrangement. (Thanks to Old_Soft_Boss for his assistance with this project).

The client would like to be able to bring up an arrangement and modify it's detail data, print a report, and then revert back to the original data for that arrangement. As it stands, changes made to any field from the detail records are immediatley applied.

Is there an easy way to allow changes to the detail records on a "temporary" basis?

 

[The_Doc_Man]

Well, one way would be to create a new, temporary master record. Then copy the detail records. Let the person do whatever. Print the report. Then when done, delete the temp record and its child records.

 

[FoFa]

Sounds like they are taking a standard, modifing for a specific job, than creating a hardcopy, restore to original format.

Question, would the client not be better served by having a standard (template if you will), being able to modify for a specific arrangement (Job), than storing that changed job data? Than later history could be run of the most common changes, and then they might be able to make business decisions based on the history? Say everyone changes the ragweed out for baby breaths, maybe that should be our standard. Or 65% of our customers change the White carnations for Pink, maybe we should charge XX more for Pink carnations?

Just a thought.

 

[jetson]

Doc - that sounde pretty straightforward. Not sure exactly how to implement.

FoFa - I like your idea, but I'm not being paid for this job. If I introduce that capability, It may end up creating more work that I'm not being compensated for.

Before you judge, it's for my Dad. He asked for help with his business so I'm helping out by writing this database. Of course, I'm not expert enough to charge anyway!

Thanks