Here're the results of looking through the core files.  Version 5.0 uses 
StructAppend and should be fine, but we aren't on a 5.0 server here at 
UMUC.  The problem is with CFGRID, etc., and 4.5 only.  The 4.0 core 
file works too.  What I did was copy section 4 of the 4.0 code to the 
4.5 file and everything worked fine.  Thanks Bert and Shawn for the input.

So, as a suggestion to the steering committee, perhaps the 4.5 core file 
could be modified to account for CFGRID and CFTREE variables?


Pete

-- 
Pete Krueger
[EMAIL PROTECTED]



Bert Dawson wrote:

> What version of the core file are you using?
> I was about to spout off that it should use a struct function rather 
> than IsDefined(), but i checked the latest version from 
> www.fusebox.org <http://www.fusebox.org> and section 4 uses 
> StructAppend, which should work OK....
>  
> Bert
>
>     -----Original Message-----
>     From: Pete Krueger [mailto:[EMAIL PROTECTED]]
>     Sent: Wednesday, May 29, 2002 7:32 AM
>     To: [EMAIL PROTECTED]
>     Subject: Fusebox and CFGRID
>
>
>     Has anybody tried to use CFGRID with Fusebox?  A coworker is
>     trying it
>     and getting an error when the core file transfers variables from the
>     form scope to the attributes scope.  CFGRID creates form variables
>     in a
>     format that cause the isDefined function to choke:
>     __CFGRID__FRMMAIN__VARIABLE.
>
>     The error we got can be seen at the following location:
>
>     http://coldfusion.umuc.edu/FB3/errors/error.htm
>
>     Any ideas on how to deal with this without touching the core
>     file?  For
>     you standards folks, is this something to be added to the core file?
>
>
>     Thanks in advance,
>     Pete
>
>     -- 
>     Pete Krueger
>     [EMAIL PROTECTED]
>

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to