While I do not disagree with that statement, again I fail to see where using ODBC on a personal laptop is going to cause such terrible problems. Server load? Nope. Problems handling the SQL? Not unless you're a terrible SQL coder (I have seem some issues when people used non-standard syntax, but they didn't know what they were doing really when they wrote it).
So again, if all else is failing, where's the problem in this? I don't see it, other than a bunch of nice-to-have's that really mean squat if JDBC can't connect. thanks -r _____________________________________ Rob Barthle Contractor - Sr. Software Developer [EMAIL PROTECTED] 202-245-6484 -----Original Message----- From: Robert Everland III [mailto:[EMAIL PROTECTED] Sent: Thursday, March 02, 2006 9:20 AM To: CF-Talk Subject: Re: Upgraded to MX7, SQL Server datasources no longer work The enviroment on the laptop should be exactly what the server enviroment is. If they use ODBC on thier server (which I highly recommend not to), then the laptop should do it. If not, then it shouldn't. Are you using full blow version of SQL or are you using MSDE? If you're using MSDE it defaults with 1433 turned off, you have to install it from a command prompt with a bunch of options in the string in order to enable it. Bob Everland ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:233910 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
