I worked around the problem by selecting everything from the table within my
date range, and then using QoQ to get the field in question. This works just
fine, but is far from optimal. I have rebooted the server, and the services,
said three hail Mary's, you name it. The only thing that worked
aliasing the column to something else
then referencing the aliased column?
-Original Message-
From: Dan Crouch [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2008 4:19 PM
To: CF-Talk
Subject: Re: Flummoxed bya simple query
I had a problem once where an CFLDAP query returned
This is a new one for me. I have been querying the same database for years. I
have hundreds of queries working on this very database on a daily basis without
issues. Today a new request came in to access a field that I have not needed to
retrieve before.
Mcaidrecda (Medicaid Recertification
not knowing much about Foxpro...
Is it case sensitive, (IE: are MCAIDRECDA and Mcaidrecda the same thing)
Tim Claremont wrote:
This is a new one for me. I have been querying the same database for years. I
have hundreds of queries working on this very database on a daily basis
without
I recently ran into an issue where the table names had to be in all caps
matching the field name in the querry. I never worried about it before
and was very confused when it happened.
Could that be the case?
Tim Claremont wrote:
This is a new one for me. I have been querying the same database
You said FoxPro which leads me to believe you might be running on Mac or
Linux. Does FoxPro have case-sensitive column names?
-Original Message-
From: Tim Claremont [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2008 10:00 AM
To: CF-Talk
Subject: Flummoxed bya simple query
That was my first thought, but I even went so far as to COPY AND PASTE the
field name from the actual FoxPro database.
Also, to further confirm, I entered the IDNo field as both IDNO and idno and it
works just fine. Conclusion is that I do not believe the case to be relevent.
I recently ran
Nope. Running on a PC. I have proven to myself time and again that the
fieldnames are NOT case sensitive.
You said FoxPro which leads me to believe you might be running on Mac or
Linux. Does FoxPro have case-sensitive column names?
I've worked briefly with it at an old job. In CFMX 6 ColdFusion
connected via the ODBC bridge and there were some unusual data results.
Has someone produced a JDBC driver for FoxPro? I don't think Microsoft
supports it anymore..
Scott Stewart wrote:
not knowing much about Foxpro...
Is it
Does FoxPro have case-sensitive column names?
It could be an issue with table names, since tables are actually files,
but not for columns.
~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
The following queries all return the same recordcount (1161 Records):
SELECT *
FROM BASICINFO
SELECT *
FROM BasicInfo
SELECT *
FROM BaSICINFO
It could be an issue with table names, since tables are actually files,
but not for columns.
I've seen issues surrounding ColdFusion caching table structures. To fix
the problem, go into CF administrator, turn off caching for that datasource,
execute your query again, and turn caching back on.
On Thu, Aug 21, 2008 at 11:24 AM, Tim Claremont
[EMAIL PROTECTED] wrote:
The following
definition.
-Original Message-
From: Sonny Savage [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2008 11:32 AM
To: CF-Talk
Subject: Re: Flummoxed bya simple query
I've seen issues surrounding ColdFusion caching table structures. To
fix
the problem, go into CF administrator, turn off
THIS works:
cfquery name=GetAll datasource=PaceCareData maxrows=10
SELECT BasicInfo.*, Identity.*, Enrollment.*
FROM BasicInfo
INNER JOIN Identity ON BasicInfo.IDID = Identity.ID
INNER JOIN Enrollment ON BasicInfo.IDID = Enrollment.IDID
ORDER BY LastName
On Thu, Aug 21, 2008 at 11:07 AM, Tim Claremont
[EMAIL PROTECTED] wrote:
THIS Fails:
cfquery name=GetAll datasource=PaceCareData maxrows=10
SELECT BasicInfo.mcaidrecda, Identity.*, Enrollment.*
FROM BasicInfo
INNER JOIN Identity ON BasicInfo.IDID = Identity.ID
Every time this has happened to me, it was a caching issue. Try to remove
caching from the datasource, if that doesn't work reboot the database machine
or restart the db services. After that restart CF and see if its all better.
I had a problem once where an CFLDAP query returned an invalid column name. It
was a similar issue where I could see it there, but I could not access it
because it had an invalid column name. I found however that I could rename it
using a method that I found on Ben Nadel's site. While your
That's not a bad idea. Have you tried aliasing the column to something else
then referencing the aliased column?
-Original Message-
From: Dan Crouch [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2008 4:19 PM
To: CF-Talk
Subject: Re: Flummoxed bya simple query
I had a problem
18 matches
Mail list logo