Re: Converting code to work with MS SQL from MySQL

> Ya, my insight is to don't do it. MsSQL is slower, Ok. Figured this much. > cost's money, It'll be free for us (our department). Our company has the appropriate MSDN subscription where we'd be able to use the SQL Server that comes with it. > and lacks support that MySQL has. Perhaps. But we've never needed the support that MySQL offers (we've always been able to find answers elsewhere) so that won't be that big of an issue, I don't think. I was more curious about issues that might come up with the code not necessarily the server. Thanks for your response in any case. :p Chris