G
Geo
Having read through much advice in this newsgroup about design of table, I now
have a problem in exporting sensible information to excel.
My main table has several 1-to-many relationships and there are about 25 tables
in the backend.
For example, my main table describes a journey where there may be 0 to 3
escorts. The junction table contains the (say) 3 records pointing to the escort
type table. This all works as expected within Access.
I created a query to include all fields of the main table (except the foreign
keys) and the fields from the other tables as required as defined in the
relationships.
My problem is that the query (and the exported excel file) will contain 3 rows
for the journey because of the 3 escorts. Is there some way to concatenate the
escorts into one column for output, to eliminate the duplicate rows?
There is a similar problem with a couple of other tables (e.g. incidents
enroute) so I am interested in a general solution.
Quite happy to use vba and/or create a temporary table as required.
Apologies if this is not the correct newsgroup (but the problem seems to be
related to tables...)
Geo
have a problem in exporting sensible information to excel.
My main table has several 1-to-many relationships and there are about 25 tables
in the backend.
For example, my main table describes a journey where there may be 0 to 3
escorts. The junction table contains the (say) 3 records pointing to the escort
type table. This all works as expected within Access.
I created a query to include all fields of the main table (except the foreign
keys) and the fields from the other tables as required as defined in the
relationships.
My problem is that the query (and the exported excel file) will contain 3 rows
for the journey because of the 3 escorts. Is there some way to concatenate the
escorts into one column for output, to eliminate the duplicate rows?
There is a similar problem with a couple of other tables (e.g. incidents
enroute) so I am interested in a general solution.
Quite happy to use vba and/or create a temporary table as required.
Apologies if this is not the correct newsgroup (but the problem seems to be
related to tables...)
Geo