Absolute Field Validation
in [Forms]
|
From: Jeanette Cunningham on 16 Apr 2010 16:43 Be aware that using exit event of controls for validation often causes more problems than it solves. Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia "Lau via AccessMonster.com" <u46349(a)uwe> wrote in message news:a6a19eff3abfe(a)uwe... > BeforeUpdate event does get triggered and it does to every family member, > which is not what I want. I will take a look at Exit event. > > Thanks. > > -- > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/201004/1 >
From: Jeanette Cunningham on 16 Apr 2010 16:53 If you use a separate field for HH, then you can check if it is Null in the before update event. To me, it would make more sense to put HH as a field in the household table. This way every household gets to have a single HH. It would free you from the impossible situation you now have on the subform. Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia "Lau via AccessMonster.com" <u46349(a)uwe> wrote in message news:a6a19eff3abfe(a)uwe... > BeforeUpdate event does get triggered and it does to every family member, > which is not what I want. I will take a look at Exit event. > > Thanks. > > -- > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/201004/1 >
From: Lau via AccessMonster.com on 19 Apr 2010 11:10 From the user's perspective, I want to keep Head of HH in the family table so I can define everyone's relationship to that individual. For now, I just put the code in OnCurrent event. Everytime there is no Head of HH, a warning would come up to remind the user. Thank you all for your inputs. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/201004/1
From: Jeanette Cunningham on 19 Apr 2010 15:58 Glad you found a solution. Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia "Lau via AccessMonster.com" <u46349(a)uwe> wrote in message news:a6c4caac65c2b(a)uwe... > From the user's perspective, I want to keep Head of HH in the family table > so > I can define everyone's relationship to that individual. For now, I just > put > the code in OnCurrent event. Everytime there is no Head of HH, a warning > would come up to remind the user. > > Thank you all for your inputs. > > -- > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/201004/1 >
From: BruceM via AccessMonster.com on 20 Apr 2010 07:09 I suggested adding Debug.Print to test the value of the strWhere. For future reference, this is a useful tool to evaluate why the Where condition is not producing the expected results. Lau wrote: >From the user's perspective, I want to keep Head of HH in the family table so >I can define everyone's relationship to that individual. For now, I just put >the code in OnCurrent event. Everytime there is no Head of HH, a warning >would come up to remind the user. > >Thank you all for your inputs. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/201004/1
First
|
Prev
|
Pages: 1 2 3 4 5 Prev: laboratory data model design Next: Compile error: Argument not optional |