Strange but True.....!

[ZABARVAN]

Hi,

We are using 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.

We are using Pervasive SQL in Novell 5.0.

Any tip, comment will be highly appreciated.


ZAB

 

[zemp]

How are you updating the tables? Using the ACCPAC COMAPI or xAPI? Or are you using ADO/ODBC?



zemp

 

[ZABARVAN]

Hi Zemp,

Thanks for your response. We are using ADO/ODBC. Any solution in mind please.

Thanks

ZAB

 

[zemp]

I would recommend using the ACCPAC API. It uses the same views and therefore business logic that the ACCPAC interface uses. This will ensure that everything is being updated properly, ensures data integrity and will let you know if there are problems.

ADO/ODBC is obviously not updating something that needs to be updated (I am not sure what).

You could write a macro (COMAPI) or VB program that updates the necessary views (or tables). Start by recording a macro in ACCPAC when you are changing the required information manually. This will tell you the views and fields that need to be updated. You will have to make some additions to have it update more than one record, but that is not difficult.

Search this forum for some example code and explanations.

zemp

 

[ZABARVAN]

Thanks Zemp, If you can provide some links to such VB Macro treads, I shall be grateful.

Thnaks

ZAB

 

[zemp]

Do a keyword search on 'xAPI' and/or 'COMAPI' and/or 'macro'. Second tab at the top of the page.

zemp