Data problems after upgrade to MX7

[jbowersce]

A few very frustrating problems have cropped up while upgrading to MX7.
Thankfully, this is our development server, not our production server, but I
have been stymied at finding the solution. I've been through siz upgrades over
the years, starting with Ver 3, and have never had these sorts of problems
previously. Basic specs: Win2k server with IIS, MS-SQL database, all service
packs up to date (including CF), fairly straighforward code base, nothing
fancy. After upgrade, several problems appear. We can downgrade back to the
previous version and all works again as it should, with the same data sources
and code base. I'm at wit's end trying to make this work, and I've run out of
ideas. I'm hoping this is some dumb setting I've overlooked, or a difference
between Ver6-MX and Ver7-MX. I've searched the knowldege base, read the
upgrade notes, prowled the forums, but no luck.

Problem number one: CLIENT variable database storage no longer works. CDATA
and CGLOBAL tables exist, are established as storage sources, and have been
functioning properly under Ver6. Error is returned as ' Invalid object name
'CDATA'. However, it IS there, and works under Ver6 using the same ODBC data
source, same user name, etc. Setting CLIENT storage to 'Registry' allows the
site to function again.

Problem number two: Missing data from queries. Properly functioning queries
return with data missing from a few fields, in a seemingly random fashion.
The variables holding the data are present in the returned query, but there is
no data present. The associated additional fields for that particular record
are intact. Again, this functions properly under Ver6. These are very simple
queries with extremely small record sets, on the order of:

<cfquery name="Query_MOTD" datasource="#application.dsn#">
SELECT * FROM MOTD
order by priority desc, ID desc
</cfquery>
This might return a half-dozen records.

So, am I missing something basic? Something fundamentally different between
version? Any help would be appreciated, I'm out of ideas.

[sdupre]

- Not sure about the CDATA problem. It certainly should find the table
itself. Check the ODBC datasource again and make sure it points to the right
place. Re-submit the ColdFusion datasource. Migration should have made ODBC
-> JDBC. I'm curious as to why you use ODBC.

- Missing data.
I'd like an example of this (template and SQL to create the tables and the
data to see this.). Does this table have variant datatypes? Is this still
using ODBC?

Stephen Dupre
Macromedia QA