I've traced this back to Windows XP SP2. When SP2 came out they changed the way SQL server datasources work. The built in firewall automatically blocked SQL server. One of the quick fixes was to use an ODBC socket instead of the MS SQL Server. I'm starting to remember now... I was having problems when this first came out, so i switched to the ODBC socket method. Everything seemed to work fine. I've been using ODBC socket ever since then.
Since I haven't done much of anything with unicode, using ODBC socket hasn't affected me because I haven't been using the "N" (nvarchar, ntext) fields in SQL server. By switching to the Coldfusion MS SQL Server datasource it works fine. So i'm now going to switch off of ODBC socket and back to MS SQL server because this is a good reason to do it. Steve -- View this message in context: http://www.nabble.com/Re%3A-Body-Content-Deleted-t1625376s621.html#a4407195 Sent from the FarCry - Dev forum at Nabble.com. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev -~----------~----~----~----~------~----~------~--~---
