On CFMX 7 you can also add the result attribute to the cfquery tag and dump
that without changing any of your other code...
- Calvin
-Original Message-
From: Dina Hess [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 10, 2005 9:50 PM
To: CF-Talk
Subject: Re: CF7 lots of new Ambiguous
On 8/10/05, jonese [EMAIL PROTECTED] wrote:
It is definatly a sql issue because when i copy out the queries and past
them into enterprise manager or query analyzer i get the same error.
I got this a few times yesterday actually - but in my case, the
queries worked fine in Enterprise Manager
Well, I'd like to see the parsed query to be certain that your problem
is fully addressed but, from what you've provided, I'd say Claude has
honed in on your issue. You need to scope the formobjectitemid and
archive columns with either the version or companynews table. This is
best practice for
Is it a SQL error, or a CF error? Because it could be CF not liking
having a query return multiple columns with the same name (SELECT
t1.name, t2.name), because query objects can't deal with that.
That's a total WAG, as I don't use SQL Server, the Data Direct
drivers, or much of CF7 (just one
Is it specific queries or apparently random? Can you post a sample
query?
--
Damien McKenna - Web Developer - [EMAIL PROTECTED]
The Limu Company - http://www.thelimucompany.com/ - 407-804-1014
#include stdjoke.h
~|
Discover
It is definatly a sql issue because when i copy out the queries and past
them into enterprise manager or query analyzer i get the same error.
It's not random it happens on the same query on every site which has 2
tables with the same column name (in this case archive).
I've changed the query
, August 09, 2005 1:03 PM
To: CF-Talk
Subject: Re: CF7 lots of new Ambiguous column name issues
It is definatly a sql issue because when i copy out the queries and past
them into enterprise manager or query analyzer i get the same error.
It's not random it happens on the same query on every site
Well, if it's happening in Query Analyzer, then it's not CF that's
causing the problem. CF's not in the mix at all at that point. Did
your SQL server get patched without you knowing or anything?
cheers,
barneyb
On 8/9/05, jonese [EMAIL PROTECTED] wrote:
It is definatly a sql issue because
WHERE formobjectitemid = 134 AND archive = 1
If you're having a formobjectitemid or archive field in both version or
companynews tables,
you will get this type of error.
~|
Logware (www.logware.us): a new and convenient
9 matches
Mail list logo
