Hi Kay, Are you asking whether it's the done thing to include instance variables (like your objectID) in the XFA value?
Well, it works, sure, but it's not something I do. Mainly because you will only be able to do this is some cases (ie where the instance value is known at the time the XFA is created). In many or most cases this will not be possible (eg when you dsp fuse loops through a recordset and creates links to delete or edit particular records). And so, just for consistency's sake, I always restrict my XFAs to holding fully-qualified fuseaction names. That way, I *always* know what's in them, and never have to wonder when I'm *using* the XFA value whether I need to add an instance value or not. Whatcha reckon? LeeBB ----- Original Message ----- From: Kay Smoljak <[EMAIL PROTECTED]> > Hi all, > > I have a small dilemma, and I was wondering (as always) what everyone > else does. It's really convenient to add variables to XFA's like this in > a switch file: > > <cfcase value="doSomething"> > <cfset xfa.back = > "#fusebox.thisCircuit#.doSomethingElse/objectID/#attributes.objectID#"> > <cfinclude template = "dsp_somefile.cfm"> > </cfcase> > > Because then your link on that display page only needs to call > #self##xfa.back#. I haven't seen this approach in any example apps, > which is what's making me nervous - is there some reason why you > *wouldn't* code xfa's like this? > > ==^================================================================ 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 ==^================================================================
