First of all, I hope this is the right forum for my problem. It really spans multiple categories, so it was hard to choose which one to post in. Also, I cut my teeth on .NET with this particular application, as everything I've done before that was in VB6. So it's possible that I'm missing something stupid since I'm not a .NET expert by any means.
My application upgrades a SQL Server database (either 2000 or 2005) that my company's clients use with another app. It upgrades the db by executing a series of SQL commands. I am using SMO with the ExecuteNonQuery and ExecuteWithResults functions, which I pass the SQL commands to.
When I build my solution (which includes an installer), and install it on test machines, everything works fine. I've even compared the database schema to make sure it upgrades everything. The problem is, that I can't debug the program on my new development computer - which is running on Windows XP 64-bit - as it gives me an error every time it makes an ExecuteNonQuery or ExecuteWithResults function call. I can debug this app just fine on my older Windows 2000 development computer, but I'd like to figure this out so I can use it on my faster Windows XP 64 machine. This leads me to believe it's a problem with the 64-bit platform. I have the .NET 2.0 Framework (64-bit) installed
View Complete Post