>Fred,
>
>Look at SQL Passthrough. With it, you can send a command to the server where it will be processed and executed.
>
>LOCAL hConn, lnResult
>hConn = SQLCONNECT(...)
>lnResult = SQLEXEC(hConn, [UPDATE table SET colum = newvalue WHERE condition])
>
>In general, you'll get much better performance by calling a stored procedure instead of passing the ad-hoc query each time.
>
>-Mike


We are using SQLEXEC() to execute the Updates and Inserts because the fields in the record sets are different depending on the amount of data entered on each record. We did not want to pass null fields accross the wire or have an extreme number of SP. We were mistaken in thinking that the SQL statements were stilling being executed locally when we used SQLEXEC(). In doing some timing trials, we are going to be using SQLPrepare with SQL execute. In 87% of the trials, the combination of SQLPrepare() and SQLEXEC() were processed in less than half the time as SQLEXEC() a lone. In a few situations the SQLPrepare() and SQLEXEC() were slower (very small data sets).

Thanx for your help.