If you have many SQL statements to run, insert or update statements for example, you can build a sql script and then run that script.

How do do this:

1) Enter the sql commands into a text file. Each SQL statement must end with a semi-colon. (If you built them in Excel save as unformatted text not table or comma separated)
2) Add the SQL+ commands 'Spool <file>' and 'spool off' to the start and end of file
This will spool the output to a text file, handy if you are running many commands.Note: these two statements do not end with a semi-colon.
3) Save the file with a name ending in sql e.g. "myfile.sql"
4) Log into SQL+ as BIOTICS_DLINK
5) Type the filename with the @ in front, you will have to type in the path
SQL> @c:\mydir\myfile.sql
6) So some select queries and check the results then type commit;
SQL>commit;

NOTE: As of 5.13.16, getnextseq will no longer be necessary, as we prepare to move towards postGres syntax in Biotics 6.

-- This is the newer syntax for insertion, which will work in Oracle after -- these changes. This syntax will be required for Postgres. INSERT INTO D_SURVEY_TYPE (SURVEY_TYPE_DESC, DISPLAY_ORDER)   values ('New survey type', 5); 

NOTE: When writing insert statements, use the getnextseq function, as shown below, to set the primary key of a table in order to prevent out of sequence errors in Biotics 5.

In Biotics 5, all primary keys are set by Oracle sequences. If you were familiar with the next_id in the NEXT_SEQ table in Biotics 4, forget about it! It no longer controls the primary key values.

See the Solution: GETNEXTSEQ function for further details.

--------Script Below This Line---------

spool c:\mydir\errors.txt
Insert into EO_BC_EXT_1 (EO_BC_EXT_1_ID,EO_ID,RECNUM) values (getnextseq('EO_BC_EXT_1'),10,'mydata');
Insert into EO_BC_EXT_1 (EO_BC_EXT_1_ID,EO_ID,RECNUM) values (getnextseq('EO_BC_EXT_1'),11,'moredata');
spool off
-------Script above This Line-----------