Hi all,

Could do with some advice, here is my situation.

My SQL Server 2000 database is essentially an archive/DSS system and has new data inserted at various times in a month by people from different locations. The inserted data is taken from a Third Party Companies server (and hence can be imported via ODBC and and a DTS package).

Each location has a seperate table for their data (hence the DTS package has to be altered each time).

So my immediate reaction was to save my SQL Server 2000 package as a VB6 module (and then convert it to VB.NET and include it with the client application) and just have the table name as a parameter. - This works fine.

PROBLEM: the ODBC links cost a daft amount per machine they are installed on and obviously without them the DTS package won't work.

So.... i have been instructed that the ODBC links can only be installed on the application server.

My initial thoughts are to use 'Remoting' (although i'm not totally clued up on this yet) and just send a parameter as a message from the client through a channel to the 'server' - This will then run the DTS package on the server rather than the clients PC.

What do you think? would you use this solution or is there a better or more simple idea that i could implement?

any help and advice would be superb

cheers