"BillCo" <co**********@g mail.com> wrote in message
news:11******** *************@g 10g2000cwb.goog legroups.com...
taking the following data:
a w
a n
b r
b y
b p
c a
getting the following result from a query:
a w, n
b r, y, p
c a
without using a function call. (Query returns several thousand rows -
if each one had to execute its own function opening a recordset it
would take unreasonably long to execute... especially since the result
is pulled over MS query into a spreadsheet (via backend on network)...
euch)
possible?
Converting from one form to the other is time-consuming. Ideally there
would be a way to meet the user requirements without necesarily deciding the
data must be shown in a two-column query. For example, you may be able to
use a report with a multi-column subreport to neatly show a list of all the
related items.
If it really has to be a query, and this is so important and speed is
critical, then you could consider re-designing the database so that it holds
redundant data (shock, horror, break the rules). Provided data is updated
via the front end you provide, you could ensure that whenever the related
table is updated, the main table updates its list of items. Sure MS Access
does not provide triggers which would give you the guarantee that the two
tables remain synchronized, but you could have a pretty good go and include
a checkup routine which would help to build this confidence.
If neither of these options appeal to you, then my final offering is to run
one function which creates one recordset to go through all records and spit
out a summary row for each header, so you create this table locally. I
think I would try this one first and see how long it actually did take
before deciding it will probably be too long. My guess is that even over
the network it would take under 10 seconds.