Re: Function sequence error with ODBCExpress

> Commiting or Aborting the inserted rows will work fine, whether you're inserting
> the rows positionally or using an INSERT SQL statement, however after you commit
> or abort (or probably before you commit or abort) you must close the result
> sets, since the ODBC driver you're using will cause the result set cursors to be
> closed on the commit or abort (and tehreby causing function sequence errors when
> you try to access the result sets afterwards). Afterwards you can open the
> result sets again.
>
> ------------------------------------------------------------------------
>
> End of quoting. Is the solution what the answers suggest? It would be
> great if the result sets need not to be closed. What is your solution for
> this?

The things above seem to be true: each dataset should be closed and then
all must be reopen which is linked to a grid. Now there is no "Function
sequence error" for us, but it is painful to close them datasets all the
time... :-(

Zoltan