Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

STRANGE BUT TRUE

Status
Not open for further replies.

ZABARVAN

IS-IT--Management
May 24, 2003
186
SA
Hi,

We are using pervasive SQL 2000 in Novell 5.0 for ACCPAC 5.0.

We frequenty need to change our Bill of Material (BOM Tables) and manual operation to update each BOM item is time consuming.
We developed a VB6 routine to update BOM Tables (ICBOMH, ICBOMD). The VB routine is working fine when we check for the Items updated in BOM. (ACCPAC BOM Screen is showing the updated quanties of components that shows the ICBOMD table have been updated)

Strangly after running the assembles to produce the finished good the assemblies table contains the BOM component figues which were before updating the ICBOMD table.

Any tip, comment will be highly appreciated.

ZAB
 
ZABARVAN, this has nothing to do with pervasive. It is an issue with ACCPAC business logic. ACCPAC business logic is so complicated that it is very difficult to properly update all that is needed via ADO/ODBC.

As I mentioned in your other post. You either need to find every place that gets updated and make the proper changes OR use the ACCPAC views (xAPI or COMAPI) which contain the ACCPAC business logic and will do all those updates for you automatically.

Double post from thread631-855441.



zemp
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top