Sorry
I guess it does sound like that. Sorry for not being clearer in my
explanation. What I have is a form that will hold this information. There
are 50 vias currently but we are always adding more. The person who received
the via paperwork will always be the same person. That also goes for the
person reviewing the via paperwork, contribution model, VP, and senior VP.
This is why I would like these names to be a constant. The updating is in
the received, review, contribution model, VP, Sr VP dates. These people all
represent different stages in the Via process. So basically. I just need to
know how to have these field auto populate for the existing via and for any
new record. Also how can I have a combo box lookup items in this form, add
new and perform notinlist event.
Thanks for any help you can provide me
>>Hi Guys,
>>
[quoted text clipped - 8 lines]
>
> John W. Vinson[MVP]
John Vinson - 24 Dec 2005 00:11 GMT
>Sorry
>
>I guess it does sound like that. Sorry for not being clearer in my
>explanation. What I have is a form that will hold this information.
No. You don't.
Tables hold information. Forms are just tools, windows which let you
manipulate the information in tables.
>There
>are 50 vias currently but we are always adding more. The person who received
[quoted text clipped - 6 lines]
>new record. Also how can I have a combo box lookup items in this form, add
>new and perform notinlist event.
Again... I don't understand your table structure. Let's be sure that's
right before we spent too much effort on the Form!
What is the Form's Recordsource?
What is the structure of this Table?
What is a "via" - you obviously know the term but I don't.
If the names are a constant, does that mean that nobody at the company
is ever allowed to retire, resign, be fired, or die?
It still sounds like you're storing a LOT of redundant information,
and that you may want to consider a better structure!
John W. Vinson[MVP]