Re: FB3, CF MX and fuseaction variable

[Lee Borkman]

Hi Andy, It's entirely up to you to choose the appropriate scope.  Request is a global scope, with all the benefits and drawbacks that always implies.  I do try to steer away from request scope these days, in the spirit of encapsulation, but the more I use recursive calls (getting more and more common), the more problem global scopes become. Many people use Attributes scope for XFAs, which gas some interesting possibilities re allowing the user to chosse the destination.  Once again, could be good, could be bad. You just need to pick the appropriate scope for the job at hand, remembering that an XFA is implemented just like any other variable, and with any variable, you want to put it into the one particular space where it will behave exactly the way you want. Sorry to be so little help ;-( LeeBB ----- Original Message ----- From: Andy I store XFAs in the request scope ... since I saw the wireframe tool generating code this way I assumed it was standard. Is it part of FB3 conventions that I should be storing these in local scope ? Andy. Douglas Smith wrote: > XFA's may be a problem since since they are, by convention, local > variable > with a dot in their name [XFA.ExitName].  Of course, they could easily > be > renamed as [XFA_ExitName].  When running your FB app in MX, just do a > global search and replace for "XFA." and replace it with "XFA_" > ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================