> 3) construct an external table and then just reference it. I think
> this sounds like a plan. Right now I actually abandoned the ADO for
> large transactions and wrote a server-client that constructs a SQL
> script and sends it to the server to be executed with that ISQL
> command line tool. That did get me around 1200-2500 tps initially
> but then slowed down severely for some reason.

Make sure you commit every 2-3000 inserts

> I really need to be
> able to have error trapping anyways which could be accomplished in a
> stored procedure that it is processing that external table.
>
> How do you construct the external table and then tell the backend
> about it?
>

that's a very simple case of FTFM - then get back to us
ALan