Access 2007 populate 12 tables with 1 master form

J

Jason Hall

I am trying to figure out how to use 1 form to populate information on 12
seperate tables. I am not good with writing code and was wondering if there
is any other type of way of doing this.
 
U

UpRider

Jason, you're going to have to use code. There are a lot of ways to do what
you want, but here's the simplest.
I'll explain how to code 1 table, just repeat it 12 times. I'm going to
assume that the 12 tables are months for this example.
First go to the form's design mode. To show the property sheet press F4.
1. Put a command button on your form. Name it cmdJanuary and set it's
caption to JAN.
2. Click on the JAN button. Then on the property sheet choose the EVENT tab.
3. On the ON CLICK event, drop down the arrow and choose EVENT PROCEDURE,
then click on the ... dots.
4. The code window should open with the cursor at the proper place to start
typing.
5. Type ME.Recordsource = "tblJanuary" (use your table name here for
January)
6. Close the code window, go to form view and try it out.
If it works, repeat steps 1 thru 5 eleven more times to add buttons for your
other eleven tables.

HTH, UpRider
 
L

Larry Linson

Jason Hall said:
I am trying to figure out how to use 1 form to populate information on 12
seperate tables. I am not good with writing code and was wondering if
there
is any other type of way of doing this.
Click to expand...

Could you help us understand the design of your database application, and
why one form would be appropriate for doing data entry into twelve different
tables. And why you would have twelve identically-formatted tables. Be
specific, concise, and precise, and someone may have an answer for you.

Larry Linson
Microsoft Access MVP
 
J

Jason Hall

I have 12 different tables that break down specific information about project
related info. The single form would be in the "one stop shop" for inputing
the project information and updating it.

I would prefer not to have 12 different forms for each table but, a master
form where I could input the information that would feed these 12 tables.

The main reason for the 12 tables is allow great flexability in reporting
and to keep related project task seperate from non-related items (submiting a
ticket to another group should not be in the same table as project contacts).
 
Top