Combined information without a query

[Abbey Murrell]

I am working on an Access Database in Access 2003. There are two main tables
that hold the most important information. There is some information that is
in both, and there is also information unique to each table. I need a
separate table that takes from them both--without using a query, and it needs
to automatically update as I add fields to either table. Is there any way to
do this? Thanks!

 

[Brendan Reynolds]

I am working on an Access Database in Access 2003. There are two main
tables
that hold the most important information. There is some information that
is
in both, and there is also information unique to each table. I need a
separate table that takes from them both--without using a query, and it
needs
to automatically update as I add fields to either table. Is there any way
to
do this? Thanks!

Not if you are entering data directly into the tables, no. If you always
entered the data via forms, it would be possible to write code to update one
table when data in the other table is updated via the form. Even in that
situation though, this would not be a recommended approach. Generally
speaking, data should not be stored in more than one table. Given the
information available, it sounds very much as though there is a fundamental
flaw in the database design that will continue to cause you problems like
this if it is not fixed.

 

[KARL DEWEY]

it needs to automatically update as I add fields to either table.
It sounds like you are running a spreadsheet instead of a relational database.
It might could be done with a whole lot of VBA or marcos with conditions.
What do you have against queries?

 

[Abbey Murrell]

Okay, that's fine. If I shouldn't be keeping the information in more than
one table, is there a way to export a table with subdatasheets that would
show the subdatasheet data in the exported file (in Excel)?

 

[Abbey Murrell]

Maybe it is more of a spreadsheet than a relational database, I wouldn't
quite know. It doesn't just contain the two tables, though, it's just that
those two tables happen to have the main information.

And I don't have a good relationship with queries. With this database,
there are several fields I need, and when I try to get all of them in a
sorted query, it becomes more of a mess than is really worth the effort.

To be completely honest, I'm not the most advanced Access user, so I have
limited knowledge on how to get the kinks out of my queries and poor database
designs.

 

[John W. Vinson]

Okay, that's fine. If I shouldn't be keeping the information in more than
one table, is there a way to export a table with subdatasheets that would
show the subdatasheet data in the exported file (in Excel)?

It is perfectly straightforward to export a *QUERY* to Excel. If you're
assuming that you must have a distinct table in order to export, that
assumption is wrong.

John W. Vinson [MVP]