Keep in mind though that making the field required means they must input something if they want to leave the field and if they get there by selecting the wrong value you force them to input something to back and change the previous field also this assumes you are forcing them to the field if the previous field is selected as such that it needs the other. Note not saying what is said below is wrong because its not just trying to point out pitfalls that I have found other programmers have overlooked in that past and I have had to fix.
--- On Fri, 4/3/09, Merrick Watchorn <[email protected]> wrote: From: Merrick Watchorn <[email protected]> Subject: Re: [Access VBA Central] One Field Required based on another Field To: [email protected] Date: Friday, April 3, 2009, 1:18 PM Joe, The easiest method would be to evaluate after input or update, that flagges the field required. If IsNull(me.input_ type) then ' Do nothing. Else ' Make value required. Msbox("You must select a value for Control.Name) , vbCritical, strDB_Title End If --- On Fri, 4/3/09, Joe <joefonseca79@ yahoo.com> wrote: From: Joe <joefonseca79@ yahoo.com> Subject: [Access VBA Central] One Field Required based on another Field To: AccessVBACentral@ yahoogroups. com Date: Friday, April 3, 2009, 10:56 AM I have a form that has a drop down field called Input_Type that has a list for Project or Discretionary. I also have another field on the form that is Capitalizable Y/N. I need to make the Capitalizable Y/N drop-down required if they select Project from the Input_Type drop down. What is the best way to go about this using VB? [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
