We are having a problem that requires an innovative solution.

Using Visual Accountmate we are writing system for a carpet distributor.

The basic structure is...

The ITEM FILE has the name of a style and color of carpet
i.e. - Atlantic-0001 (this is a unique item)

For each Item there are an unlimited number of ROLLS OF CARPET FILE
i.e. Roll # 0001, 0002 etc.

For each ROLL there are an unlimited number of TRANSACTIONS
PER ROLL FILE.
For example, if Roll 0001 has 100 feet of carpet on it
20 feet could be committed for sale to Company A
50 feet were sold to Company B
10 feet are on a sales quote for Company C
5 feet were discarded as damaged
leaving 15 feet on the roll

When the end user wants to assign X feet to a sales order he or she
sees both the summary and detail status of all the rolls under this
item.

The problem is in showing REAL TIME status. We would prefer NOT
to update the real databases constantly because if the user assigns
10 feet from roll 1 to an order...and then changes his mind, we need
to re update 6 permanent databases.

So, what we have been doing is building a temporary file, based on
the current status. We then have been updating, when the whole
order is saved.

The problem with this approach is two fold...
If I assign 10 feet to roll 0001 ... then create a new line item
for the same Item # (same carpet style)...we are not seeing the real
status of the roll, since we do not update the permanent file until
the order is saved.

If another user sells the same item, he is not seeing the real time
status...and may accidentally over sell the roll.

What we need is a way to show the real status of each roll, but hold
the permanent update until we save the order. My initial thought was
to add a field to the roll transaction file. This field would be filled
with something like "username". This record would be included in the
roll status update...because it is a real record in the roll trans-
action database. When the order is saved, the records for this roll,
with this username in the new field would be deleted, and the update
would proceed normally.

However, I am open to suggestion on a better method.

Glenn