VB.Net and ADO

[ViperPit]

We have an application that was written in VB6 and connected to a SQL Server using ADO. It runs on 20 machines, and has been running without problem for a couple years.
I just finished converting the project to VB.Net and the application runs fine on one machine at a time, but when you start it on multiple machines, they start to get messages "You process was deadlocked with another process, and you have been chosen as the deadlock victim".
Now, although the project is now in VB.Net, the connection to the SQL server is stil the same ADO connection code (None of the actual query text has changed).
I am wondering if this is a problem with VB.Net handling ADO connections differently than VB6 did.
I am thinking about changing the connections to use ADO.Net, but would like to get an idea as to whether than will fix it, or just be an effort in futility.

Has anyone ever had a project that working perfectly in VB6 connecting to SQL via ADO, and then converted the project to VB.Net and had connection issues?

Thanks for you help.

 

[NoCoolHandle]

First.. I don't know why you are getting the deadlock issue, you really should use profiler/trace to check this one out.
(I suspect you have an open transaction - sp_who or sp_who2 or sp_Lock might give you some clues also)

Second.. YOu should be useing the SQLClient object not ADO from dotnet. It works but sqlclient is a bettter group of objects to work with. Faster, cleaner and more scaleable.