>Surely sounds weird. I almost agreed with James that SP would be the best, having done some convoluted ones myself, but what you're doing is simply easier to do in Fox, and the speed gain is not certain.
>
>Maybe then it doesn't have to be a COM object - a simple .exe which would run on the server would do. It could stay in a timer loop all day, just checking the flag in the table, and then, when it sees the flag set, it would
>
>- disable the timer
>- pull the needed data from the server
>- grind them, updating the flag (as "in process")
>- push the results back to server
>- reset the flag and log what it did
>- enable the timer.
>
>Note that I didn't put any server updates in the grinding part. Any server writes that can be deferred to the end of the process, should be deferred.

It certainly is a convoluted process, but it gives the best distrobution of product we can think of. What you describe is just what I was thinking. During the processing, ALL of the updates occur only in the cursors. At the end of the processing, just the results get published back to SQL. I just wanted to make sure there wasn't a much more elegant solution out there these days.

Thanks.