I've never tried to do nesting this complicated. I would have to test with data. Sorry, think you are on your own.
I've never tried to do nesting this complicated. I would have to test with data. Sorry, think you are on your own.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Thanks, Rawb.
Adding , after TimeDay changes the error to, "Cannot find input table or query Q2..." But since I need Item_KEY, ReadingDate, SalesProd1, DailyProd2, DailyProd 3 accessible, then the structure of the query is probably incorrect. I understand it would be difficult for someone else to interpret what I need and be able to provide an answer. I'll read up on the links and see what I can figure out. I have a few options, but it seems the nested query approach is the best. It saves from using countless named queries in the db, and saves from what would be an ever expanding table size stored locally. So I guess it's just getting over the complexity hump.
I may prepare a test database if I continue to encounter hurdles. Thanks again June7 & Rawb for the feedback
Hey I'm reading the allenbrowne links and have a question. In VBA, can I create a stacked query without saving the query in Access?
I guess this would be querying an ADODB.Recordset with another ADO query?
AFAIK, no. Nested SQL statements can be used to open a recordset.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.