11.1.98    <SQLEXECUTE>

Description:   Executes a complete SQL command line placed in the buffer by a series of <SQLPREPARE> commands.

Syntax:         <SQLEXECUTE>

Arguments:    none

 

See Also:       <SQLDIRECT>, <SQLPREPARE>

 

Examples:      # WebDATA is an ODBC DSN attached to an Access Database or SQL Server DB

                # COMPARE with SQLDIRECT entry

<SQLPREPARE>CONNECT SESSION 1 TO WebDATA

<SQLEXECUTE>

<SQLPREPARE>USE SESSION 1

<SQLEXECUTE>

 

#Insert data into table

#For ODBC Databases that do not support level 2 commands (e.g. Access)

# break into two lines using SQL prepare

<SQLPREPARE>INSERT INTO Table1 VALUES (@%TTMDATE,

<SQLPREPARE>@ %TTMTIME, @AMPLITUDE,

<SQLPREPARE>@TIMER)

<SQLEXECUTE>

This command is used to execute an SQL command that is more than one line long.  An <SQLPREPARE> command must be used to form a complete SQL command line before an <SQLEXECUTE> .  <SQLEXECUTE> clears the buffer.  SQLPREPARE and SQLEXECUTE allow a single large SQL command to be written using multiple lines in a script.

SQLPREPARE with a SQLEXECUTE is the equivalent of a single SQLDIRECT command.  However, the Script editor effectively limits an SQLDIRECT command to 1000 characters.   For longer than 1000 characters on one SQL command line, use SQLPREPARE and SQLEXECUTE.  SQLPREPARE has a 16,000 (16k) character buffer limit.

<SQLEXCUTE> will interact with the related script Action commands SQLPREPARE, SQLDIRECT and SQLEXECUTE allowing a script to initialize or open an SQL session and user keymacro commands to enter data. For a complex series of SQL commands, a script may be easier to implement.

WebAccess supports both Level 1 and Level 2 SQL statement.  SQL is an acronym for Structured Query Language.  Please refer to an SQL manual for complete syntax of the SQL language. These commands are used to interact with a Database file like Access or SQL Server through an ODBC DSN