Same field names - two different tables

[skydiver]

Greetings. Access 2010. I've created a table utilizing certain fields that may be necessary during scenario A. However, if scenario A doesn't apply to the situation...then scenario B can come into play. The fields are the same, but can be recorded in either situation...not both. When I run a query or a report will I be catching data from either table? Hope this makes sense. I'm trying to keep this as simple as possible. Thank you!
:banghead:

 

[plog]

It depends on your SQL. Can you post sample data from your tables and what you would like a query to return based on that sample data?

 

[skydiver]

Elaboration. Basically, I would be plugging data into one of two tables with some of the same fields and would like to run a query/report on those particular fields and get one result. Two different inputs...one output. See attachment. Thanks!

 

[jdraw]

I can not open your attached file.

Tell us more about your A and B.

Seems if you had just one table, and an additional --- RecordType that you fill with A or B as necessary would solve the issue.

Since that seems too simplistic, I suggest you tell us more about your situation.

 

[skydiver]

Scenario A (Design View)
Field Name
Data Type
Example1
Number
Example2
Number
Example3
Number


Scenario A (Datasheet View)
Example1
Example2
Example3

1​

4​

0​

0​

3​

2​

7​

5​

9​

2​

1​

14​

4​

2​

0​

0​

0​

0​

5​

3​

1​

Scenario B (Design View)
Field Name
Data Type
Example1
Number
Example2
Number
Example3
Number


Scenario B (Datasheet View)
Example1
Example2
Example3

0​

0​

3​

2​

0​

0​

0​

0​

0​

0​

0​

0​

0​

0​

6​

2​

4​

2​

1​

1​

1​

So, where data is not collected in Scenario A, it may be recorded in Scenario B. When I run a query or a report I want the ability to find totals from both tables.

 

[skydiver]

This doesn't look right...standby for explanation.

 

[skydiver]

So, Scenario A table and Scenario B table. Where data is not collected in one table, it might be recorded in the other table. Two different tables for two different scenarios, but when I run a query or report I want to pull the data from both in order to get one result.

 

[skydiver]

I think what I can also do is name a field Example1a and Example1b in order to separate one scenario from the other. It might be easier to do it this way. Still thinking...

 

[Galaxiom]

I second Pat's suggestion. Persisting with this seriously denormalized structure is going to keep running into problems.