Now, that made sense. Thanks, Russ.
I solved the problem I had by hardcoding the calls to my database in all my
queries rather than using an application variable for the datasource name
and by removing the line in my CFAPPLICATION tag that set client storage in
the database. Got a call in to the ISP to modify the datasource, but I'll
check on the server version. I can't imagine that they're using 4.0 or
earlier. It's CFHosting.
Your other question about whether I had wrapped my #request.flagdsn# in
CFOUTPUTs was a good one. I'll check that out too when I get home.
This list is the greatest!
Regards,
--John
"Johnson,
Russ " To: Fusebox <[EMAIL PROTECTED]>
<Russ_Johnson cc:
@csx.com> Subject: RE: Request scope
12/19/2000
09:56 AM
Please
respond to
fusebox
You need to check which version of CF is on the ISP server. The request
scope was not introduced until 4.01. If they are on 4.0 you will have to
convert all of your request scope vars or find a new ISP.
Russ
-----Original Message-----
From: Jim Priest [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 18, 2000 11:05 PM
To: Fusebox
Subject: Re: Request scope
Could it be a case sensitivity issue? Is the server NT or ???
JA> Error resolving parameter REQUEST.FLAGDSN
JA> The object FLAGDSN is not present in the scope named REQUEST.
Is this statement wrapped in a <cfoutput> tag?
JA> is calling 'datasource="#request.FlagDSN#"'
jim
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
