> The Enabled state shouldn't change when the checkbox > doesn't change, so why do you need the code to fire?
I was having everything revert to Enabled for each new record that the user was adding. I was then going to disable certain fields depending on the value of the checkbox. I suppose I *could* leave the Enabled status of each field the same, rather than resetting them all to Enabled, but was wondering why the code wasn't firing when just "passing through" the checkbox rather than actually clicking on it. > Also, sorry for being nitpicky, but seeing the code you > wrote brought back many bad memories of code that was broken > due to really long references like you had. Here's one way to > accomplish the same thing with a lot less chance of breakage: No apology necessary. As I've said in one of my older posts from a couple of weeks ago, I'm very much the VFP rookie. I've taught myself enough to create an app that's working very well for one of our locations, but am definitely still learning this stuff. So, much appreciated! John _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
