Adding records to multiple tables

[hazel4832]

I have an Access database with three tables. One is BP, one is Address
and the other is Dates. Basically what this database is going to be
used for is to keep track of all the opening and closing dates of each
store (BP). I need to be able to add BP's to the database. I am trying
to figure out how I can have one form with all the data in it that I
need and have it distribute the correct information to the correct
table. Any help would be greatly appreciated.

 

[Jeff Boyce]

Unlike a spreadsheet, you don't need to (and some would argue, shouldn't) be
"distributing ... information" across more than one table. That said, if
you aren't trying to redundantly store data, then tell us more about the
relationships among those three tables.

"How" depends on "what" ... and we don't know how those three are related.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[hazel4832]

Unlike a spreadsheet, you don't need to (and some would argue, shouldn't)be
"distributing ... information" across more than one table.  That said, if
you aren't trying to redundantly store data, then tell us more about the
relationships among those three tables.

"How" depends on "what" ... and we don't know how those three are related..

Regards

Jeff Boyce
Microsoft Office/Access MVP

I deleted one table, which was just redundant. Now it's two different
tables with different information in each. I just wanted to be able to
use one form to input information into each of them. Their PK is BP#.
There is a one-to-one relationship between the two tables.

Table 1
BP# Address City State Zip

Table 2
BP# Open1 Close1 Open2 Close2 ...

 

[Jeff Boyce]

Sorry, I still don't understand your "domain" and the underlying data well
enough to offer suggestions.

I do notice that you appear to have 'repeating fields' in the second table
.... this is a very spreadsheetly way of storing data, but is NOT appropriate
for a well-normalized relational database. So what, you ask? So Access is
optimized for well-normalized data ... both you and Access will have to work
overtime to overcome 'sheet data.

Regards

Jeff Boyce
Microsoft Office/Access MVP

Unlike a spreadsheet, you don't need to (and some would argue, shouldn't)
be
"distributing ... information" across more than one table. That said, if
you aren't trying to redundantly store data, then tell us more about the
relationships among those three tables.

"How" depends on "what" ... and we don't know how those three are related.

Regards

Jeff Boyce
Microsoft Office/Access MVP

I deleted one table, which was just redundant. Now it's two different
tables with different information in each. I just wanted to be able to
use one form to input information into each of them. Their PK is BP#.
There is a one-to-one relationship between the two tables.

Table 1
BP# Address City State Zip

Table 2
BP# Open1 Close1 Open2 Close2 ...