Drew, See the following ColdCut I wrote in the Teratech ColdCut database. It tells you how to deal with misbehaved MDAC installs. Hope it helps you! Eron http://www.teratech.com/coldcuts/cutdetail.cfm?cutid=89 -----Original Message----- From: Steve Pierce [mailto:[EMAIL PROTECTED]] Sent: Friday, December 08, 2000 12:04 PM To: CF-Talk Subject: RE: ODBC errors with MS Access after MDAC 2.5 The update was to MDAC 2.5, not 2.6. My fault for getting the numbers mixed up. But the CF code broke after upgrading to MDAC 2.5. Also for more background the server is running NT4 SP6a, Website 2.5.8 and CF Enterprise 4.0.2. The CF code worked fine with MDAC 2.4, it was after upgrading to MDAC 2.5 that this one CF template started throwing a PCode error. - Steve -----Original Message----- From: Dru Whitledge [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 07, 2000 10:13 PM To: CF-Talk Subject: ODBC errors with MS Access after MDAC 2.6 After upgrading to MDAC 2.6 (contains ODBC) at my ISP I am now experiencing memory errors for MS Access queries that once ran without a problem (and still do on my MDAC 2.1 server). The CF server provides the following error message -- (and of course stops execution) CMemoryException: unknown cause PCodeRuntimeContextImp::executeSQLTagCFQuery::endTag Has anyone else had this problem? Anyone aware of any fixes? As I started into this I had assumed that the new MDAC 2.6 upgrade simply tightened up some requirment for correct SQL syntax -- now I'm not so sure. One query I'm rebuilding seems to fail on a adding a simple concatenation to create an alias field -- (field1) & (field2) AS Field3 while (field1) AS Field3 works fine. That's hard to workaround. Thanks, Dru ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
