Database

At any time, only one table in a session can have the IDENTITY_INSERT property set to ON. If a table already has this property set to ON, and a SET IDENTITY_INSERT ON statement is issued for another table, Microsoft® SQL Server™ returns an error message that states SET IDENTITY_INSERT is already ON and reports the table it is set ON for. If the value inserted is larger than the current identity value for the table, SQL Server automatically uses the new inserted value as the current identity value. The setting of SET IDENTITY_INSERT is set at execute or run time and not at parse time. :|

Have you double-checked the UDL-files contents? Try using the UDL on a clean connection object: Dim cnn As New ADODB.Connection cnn.Open "File Name=c:\test\file.udl"

Take a look at http://download.microsoft.com/download/vc60pro/sample/1/WIN98/EN-US/Adovc1.exe It's a simple sample using the #import directive, which makes it pretty easy to use ADO to do all the stuff you want... Simply include MDAC in your setup's, it can be downloaded from http://www.microsoft.com/data/ All database drivers are included in MDAC, so as long as you are using Access databases or SQL Server, you know the drivers are there... Hope this helps. - Anders

Just chage the client on both machines to use TCP instead of Named Pipes and the problem is gone :) (I hope) Well, at least, if the errormessages is something about a "Overlapped Result" it works... - Anders