On the same server, I have two separate BSV systems running.
Same MSSQL database instance, same Aware installation, but different BSVs in diff. databases.
Latest 8.6 build.
I discovered attributes and can read/write data into an external table.
But when I try to create a new record, I'm stumped.
My external table has EXT_ID for the primary key ID field in the main system.
If I want to create a record into that external table, it would appear I have to create the unique key (ID) value.
Now I cannot access the Sequence from that external db, so what am i to do?
I thought about picking a really high number and setting EXT_ID to be auto incremented.
In the CREATE statement, I use
CREATE xxx WITH
...
comms.EXT_BASTIMESTAMP = CURRENT_TIMESTAMP,
comms.EXT_BASVERSION = 1,
comms.EXT_ID = NEXT_SEQUENCE_NMB('comms','EXT_ID')
My first attempt left a -1 as the ID inside the MSSQL table. It created it, just not with a PK.

Its a lot to track down.
Is it my syntax on the NEXT_SEQUENCE stmt, or can NEXT_SEQ work on external files, etc etc
Just wondering if anyone else has done this.
thx