[AccessD] Turn a recordset into an actual table

[John Colby]

I'm thinking you're likely to die before a date with Halle Berry.

As for your more real life problem.  Just build a table one time with all
of the fields that can be in the result set.  Now append the resulting
recordset into that table.  Having done that you can sort on fields etc.

It will be denormalized but it appears to me that is what you are doing
after all.

On Tue, Oct 26, 2021 at 11:26 AM Arthur Fuller <fuller.artful at gmail.com>
wrote:

> Perhaps I am asking all the wrong questions. Interesting and educational as
> this thread is, I don't seem to be getting closer to the solution of my
> current problem. A little background:
> The  app concerns a discipline called Safety Assessment Engineering. The
> top of the hierarchy is Customers, then Projects, then Workstations
> (machines), then Risks and finally Solutions (maximum six per Risk).
> The existing code works well. Depending on the number of Machines as
> revealed by a DCount() call, we choose among several report layouts, and in
> addition also do an Export to Excel/ The original code, which a colleague
> and I wrote, is fired from a button on a form, which assumes that exactly
> one Project has been selected. Having selected the Project of interest, the
> user is presented with a list of its Machines.
> The code depends on the existence of a named RecordSet. The current
> implementation anticipates a RecordSet whose scope is a single Project, and
> may or may not include all Machines associated with that Project.
> I have been asked to expland this to allow the user to select multiple
> Projects *by Customer) and then multiple Machines within each project. I
> have created a dialog which contains a pair of Extended Select  ListBoxes,
> and also a button that builds a SQL In() clause from the selected Machine
> IDs. I plug the resultant In() clause into a queryDef. But I want to be
> able to browse the result as if it were an actual table. Downstreaam there
> will be consequences in terms of report formatting and so on, and I'm ok
> with that. I just wish that after creating the RecordSet with multiple
> Projects and Machines, that I could browse it and check for (in)accuracy.
> To begin with, I need a tool that, given the name of a QueryDef, shows me
> the SQL. From that I can build a table and browse it and ensure that
> everything is working correctly.
> And finally, in case I die before completing this mission, I need a date
> with Halle Berry. Anyone know her?
>
> On Tue, Oct 26, 2021 at 9:43 AM Bill Benson <bensonforums at gmail.com>
> wrote:
>
> abaseadvisors.com <AccessD at databaseadvisors.com>
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting