DTS 2000 package designer and SQL Server 2005

I am not sure where to ask this question. So I figured here may be ok

I have several DTS 2000 packages and I have SQL 2005 installed on my local machine. However the rest of the company is still using SQL 2000 (for now). So I do not want to convert them to ssis yet. One of the things we just did to the packages is make all flat files use \\localhost and any servers point to (local). Now in ssis this works fine but using the DTS 2000 package designer it does not like either of these at all. The reason we wanted to do this is so when we switch out servers there is no changes to our DTS packages.

I have found some problems using \\localhost as a UNC path in SSIS packages (for whatever reason it occassionally returned a duplicate name exception). Instead, try using \\127.0.0.1\ssis , which is essentially a loopback share onto the package execution host machines. Naturally, you would need to create the share on each machine. I haven't used or looked at DTS in eons so I couldn't tell you whether that works with DTS let alone migration issues.|||

yes the 127.0.0.1 worked for paths, however the (local) for servername does not. I Think it is a bug because the DBA that has SQL Enterprise manager can put (local) for servers and localhost for paths. But when I use SQL Server management studio (2005) and the DTS 2000 package designer neither works (except like I said 127.0.0.1).

Now if I build a new ssis then I can use (local) but you are right I think you still have to use 127.0.0.1 for paths.

Thanks for your reply.