Ironically, every time I upgrade, I find myself with LESS functionality, not more.  This one is a real problem though and I'm hoping someone has been able to think out of the box on this.

Here's the situation.  When we do inventory, we try to fix the transaction history to be as accurate as possible rather than take an adjustment.  For example, we freeze inventory and at the time a particular item has a quantity on hand of 25, but a count of 50.  So when I get the counts back, I go and research the item and find that a work order was not properly received into stock.  I will go back to 12/31 and do a work order completion transaction.  

Meanwhile in Access I have a table that includes all the fields from the IM_PhysicalInventory file, plus some additional fields like one called Correction.  Previously (prior to moving from 4.3 to 4.5)  when I was ready to post inventory, I would use a query to generate a table (for import through VI) for that would add the "correction": field to the frozen quantity, so in the example above the quantity on hand in the IM_Physical Inventory file would now be 50, the count would be 50, and there would be 0 variance.

But now, I find that I can longer import the Quantity on Hand to Inventory!!!  There are two potential solutions I can think of, and neither of them are something I really want to do:

1) refreeze the items, and then add to the count of each item the sum of the transactions since 12/31.  But I would rather not do this if I don't have to.  

or 

2) use the r/w odbc to update the quantity on hand in Im_PhysicalCount by force.  Yes I am aware of the issues with this, but the r/w driver actually works quite well since the tables have been moved to the business framework.

Anyone have any better solutions?

Thanks!

Matt Kaney

Biopac Systems, Inc.