--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
"Kate" <Ka...@discussions.microsoft.com> wrote in message
news:C58A463C-618B-4CA9...@microsoft.com...
>I would like to know how to program the database so the data can be entered
> simultaneously to two different columns in two different tables at the
> same
> time. For example, I have Table 1, and one column within that table
> called
> "proejct #". I have Table 2, again with one column called project #. How
> do
> I set up the database so I can enter projec numbers to these two tables
> simultaneously. Any help would be greatly appreciated.
>
> Kate
>I would like to know how to program the database so the data can be entered
>simultaneously to two different columns in two different tables at the same
>time. For example, I have Table 1, and one column within that table called
>"proejct #". I have Table 2, again with one column called project #. How do
>I set up the database so I can enter projec numbers to these two tables
>simultaneously. Any help would be greatly appreciated.
>
>Kate
You wouldn't, generally. Creating an empty "placeholder" record in Table2 is
very rarely a good idea!
If table1 is related one-to-many to table2, typically you would use a Form
based on table1 with a Subform based on table2, using [Project #] as the
master/link field. This will ensure that Table2 inherits the project number as
soon as there is any data entered into Table2 (but not before, because it
isn't needed before!).
Just a side note - you may want to avoid the use of special characters such as
blanks and # in fieldnames. # is a date delimiter and Access can get confused.
A field named ProjectNo will be less hassle and will let you upgrade more
easily to SQL/Server if that should ever come to pass. If you do use Project #
then you must ALWAYS enclose the fieldname in brackets - [Project #].
--
John W. Vinson [MVP]