On Fri, 13 Jul 2007 14:01:36 -0400, "Jason Lopez"
<(E-Mail Removed)> wrote:
>I am trying to put some VB code in as a form of validation on an Access
>form. What I am looking for is essentially the ability to check 5 different
>controls for data contained within. The controls are for dates that are
>tied to a table that records the training completion dates. In an effort to
>avoid out-of-sequence training or edits to the data after the initial entry,
>I am wanting to put in this code. It essentially enables the field for
>putting in data but disables subsequent fields to maintain the training
>sequence.
>
>This is what I have so far (and it is *long* down below). At this point, I
>cannot seem to get it to work right. It immediately locks down the form
>when there are dates in the fields. The only other thing that I can think
>of is to have this same VB code for the BeforeUpdate, On_Click and
>AfterUpdate events.
Stepping back a bit... if you have one *field* for each kind of date, you're
perhaps limiting your flexibility in terms of table design. Suppose you want
to add a *sixth* type of training? You'll need to restructure your table,
rewrite all your queries, redesign your forms and reports, rewrite all your
code... ouch!
Could you instead consider a four-table solution:
Employees
EmployeeID <Primery Key>
LastName
FirstName
<other bio data>
Courses
CourseID <Primary Key>
Description
<other info about the training>
Schedule
SeqNo <what order the courses must be taken>
CourseID <which course>
<other info, e.g. comments, valid reasons to take a course out of order or
skip it, etc.>
Trainings
TrainingID
EmployeeID
CourseID
CompletionDate
<comments, pass/fail, retakes, etc.>
You could then simply *add a record* to the Trainings table; the form's
beforeupdate event could be used to ensure that you're not entering a course
out of sequence; it would make reporting MUCH easier.
John W. Vinson [MVP]
Similar Threads
