Bob,

Thx for the idea, I've tried it but only using T-SQL at the server side, it isn't that evident ; only finding out which files are in a certain directory on the server doesn't seem that easy (isnt even possible AFAIK) ...

In the meantime I've found an alternative : instead of sending one insert at the time I send several in one SQLexec(), delimited with semicolons. I've tried to send 200 inserts at once whithout any problem. Speed gain is easy up to 8.

In my message I stated an insert rate of 400 rows/sec but that really was only 60-80 rows/min (over dial up). Now I'm getting easily 500 rows/min . The only thing that is important is that the block of insert's is considered as a transaction. If one of them fails, all previous are rolled back within that block, which is fine as long as you're aware.

Pascal.

>Is there a set number of users on your system, where the file names can have like a id number+'mydailydata.txt' have the sp loop thru all the dropped off data daily, hourly, whatever makes sense, and import it all then.
>Then remove the dumped files.
>Just a thought.
>Bob Lee