Scripting

Our customer is trying to replace an Access program that calculates pricing for the mixed-feed products they produce and sell retail. We could treat the feed product as either IM items or Misc Items. For now, consider Misc Items only, capturing the 3 account codes and description. (Do NOT worry about PO or inventory costing issues for now.) The price of each Misc Item is a function of several cost factors, including ingredient costs. the price also consider several overhead elements, entered more like Kentucky Windage than anything else. One possibility is setting up a scheme to update these in an interface which enters the values into a UDT with ProducCode as the row, and the several factors in the columns. THE QUESTION IS, what might be the most user-friendly interface to that table? We doubt that a straight Custom Office form will be acceptable to them. But if we do an Excel/Access interface, must we import the data to the UDT via VI, or can we use BOI coding to read and write to it? (We would use scripting to update the $$$ values in the Common Item table from this UDT.) Thanks for your thoughts!

I would certainly go the BOI route. I would also write this in such a way that the field names were identical in both Access and the UDT so that your BOI code could make the assumption to populate the UDT with all the fields that exist in the Access table without having any field dependant code.

Thanks, Dan. That helped us with this assessment.