Auto increment GLBCTL

[hbedelaar]

What is the auto increment mechanism for the primary key of table GLBCTL? Column name BatchID

 

[Jay Converse]

It's built into core business logic. To program it, use

GLBCTL.RecordGenerate True

 

[hbedelaar]

Can you describe the working of procedure GLBCTL.RecordGenerate built into the core business logic?

Some of our older services integrated into accpac inserts directly into the tables. To avoid PK conflicts, the services started at high BatchID values. This is crap. Although we can't do much about the way the integration was done, we can change the source of the generator of BatchID. It would be much better if we at least attempt to follow the PK generator employed by the business logic.

 

[Jay Converse]

Direct inserts will corrupt the database. Use the Accpac COMAPI to integrate.

 

[hbedelaar]

Not an option. We don't have the source code for these services, but they've been running a long time without causing some sort of corruption. We're trying to avoid problems by PK unique violation through the use of triggers.

 

[Jay Converse]

GLOPT.NEXTBTCHNO, use at your own risk.

 

[ettienne]

Oh geez... BAD idea inserting into the tables.

 

[hbedelaar]

As I said... no choice in this matter. The COM API or SDATA API would have been the right choice.

For any other DB admins out there struggling with this answer: GLOPT is not a table. Some view (not a DB view) provided by a DLL function call. On our implementation of accpac, the table containing NextBTCHNo was GL01

Thanks to tuba2007 for pointing us in the right direction.