If I read your message right and this variable state affects multiple users who use your application, then it sounds like maybe something that should be a part of a db query. That way the 'complete' or 'incomplete' state of the form can persist across application (CF) restarts.
If its something shorter term an application variable might be a better answer. This could be a cached settings query run from application.cfm, or just another output field in an already-existing query? Seems like you could do this several different ways depending on app/db design. --------------------------------------- Matt Robertson, MSB Designs, Inc. http://mysecretbase.com - Retail http://foohbar.org - ColdFusion Tools --------------------------------------- ---------- Original Message ---------------------------------- from: Janine Jakim <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Fri, 6 Dec 2002 14:20:08 -0500 >I generally make client variables those that aren't going to change while >the user is logged in. (ie:Group type=admin/etc) >I have an app that will have several different forms per student. (some with >one to many relationships/some with one to one). >If a case manager says the forms are complete =All forms except one becomes >read only. >If the case manager says they are not complete = All forms can be edited by >a variety of users. >I'm wondering what type of variable this Complete=Y/N should be... > >It will have to follow each student through all the forms, but reset when a >new student is chosen. I'm assuming client variable isn't appropriate for >this.... >Thanks for the input. >j > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting.
