This is an old revision of the document!

'Normal' Processing Steps

Create a new schema using either NovoMotion NOVO.GEN.SCHEMA or NovoMotion Schema Editor.
In the NovoMotion Schema Editor, establish the connection information on the SQL Options tab and activate the schema.
In the NovoMotion Schema Editor, use the SQL script creation (Creating a SQL Script) process to generate a SQL script to copy and execute in the SQL database.
If the ODBC datasource is new, create it by either adding a data source through the Administrative Tools (Windows) or ding the data source to the odbc.ini record (Unix).
Use the LOAD.BCI.ACTION process to test a load from the U2 server to the SQL server.
Correct dictionaries, connections, or schema records as needed.
Once there are no identified issues, use NOVO.E.T (NovoMotion Trigger Generator) to enable an UPDATE (and usually a DELETE) trigger on the U2 file.
Use the LOAD.BCI.ACTION process to load all the records from the U2 environment to the SQL server.
Check the SQL server to verify results.

Error Message	Analysis Steps
No BCI.ACTION record created	Verify the trigger is on using LIST.TRIGGER. If the trigger exists, try logging off and back on. If the file is the TM, make sure the table number has been added on the NovoMotion Interface Control Trigger Controls tab.
No Schema exists for filename	Verify the schema is flagged as Active in the NovoMotion Schema Editor
Connection does not exist	Verify the correct login and password are entered in the SQL Options tab of the NovoMotion Schema Editor. If they are, verify the datasource is set up. If it is, verify the login has permission to the database on the SQL server.
Invalid Object Name error	Verify the database name on the SQL options tab of the NovoMotion Schema Editor is fully qualified i.e dbo.filename

NovoRoi Systems DokuWiki