Well, here is another consideration that may be more "correct", but will generate a bit more coding for you.
You are using the data in two different forms. To me, the first thing that came to mind is that you may need to different objects. Don't confuse data with objects. That's a big rule in OOP, or so I hear. (I'm not an OO expert by any means.) It may require two different sets of related CFCs, but it may make more sense in the future. Then, you drastically cut down on the number of "IF" statements and other logic processing that is unneeded in the "lighter" version of the form. M!ke -----Original Message----- From: Matt Williams [mailto:[EMAIL PROTECTED] Sent: Thursday, March 30, 2006 2:22 PM To: CF-Talk Subject: Re: OOP/CF - Update Function in a DAO Mike, I thought of that too. It would probably work. The issue I have with it is if a field were to get added at some point, I'd have to make sure every possible form got that field added. Keep thinking. I know there has to be an easier way. I fear it involves mucho 'if' statements. Matt On 3/30/06, Dawson, Michael <[EMAIL PROTECTED]> wrote: > > How about just passing *all* fields to the form? Then, you would > create visible form elements as needed and the rest of the fields > would be in hidden form elements. > > M!ke ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236602 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
