Search results

Initially I did want to find the solution to this and move forward in ADO. However if the issue is ADO becoming involved in processing wildcards specified in the existing Access Query objects I am loath to change them as they have been tested. So using DAO which either defers to access to...

Thanks LPurvis. I had read your earlier reply too quickly; thought it was from Gizmo again. Would have said hello had I noticed it was a new-to-this-thread-user!

That is another query. I have tried to explain that I have three levels of nested queries. At any rate I am now on the right track; thank you for your help.

Hi Gizmo, I converted my code to use DAO and it worked fine returning the result set I expected. Obviously DAO and ADODB access and/or process references to Access Query objects differently. Can you point me in the right direction to get up to educate myself on this? I have always used...

Yes, as I stated in my first post I am retrieving data from a nested Access query. The SQL for [VW-DIY Paypal Debits] is: SELECT [VW-DIY Paypal All Processed].Date AS TransactionDate, [VW-DIY Paypal All Processed].Description, [VW-DIY Paypal All Processed].[Transaction ID], Abs([Gross]) AS...

Gizmo, in my reply I asked you if that was what you wanted. Sorry if I was not clear. Without the where clause 130 records were returned from VBA and 116 records were returned from Access Query. The individual rows previously returned still exist in the larger result sets. What are you...

Without the WHERE clause? Here is something strange. If I change my Access Query to a make table query and run the same SQL statement but target the resulting table I get the same result from Access Query and VBA. Are there some limitations to running SQL against an Access query that I am not...

First off, thank you for the input! Gemma - I cut off the EOF looping bit; sorry for the confusion. I should also have mentioned that the row returned by VBA does not exist in the query's result set; it was filtered out by the query! It is almost like VBA is referencing the wrong query object...

I don't think my original post was clear. When the SQL is run in VBA I get a single row where transaction ID is 87T44061HP454861M When the SQL is run direct as a query I get a single different row where transaction ID is 5K494903EW901800E So both results are not included in either query...

Both return no results as expected. Were you testing for corruption?

Hello, I've often found answers using this forum's search function but am stumped and am hoping you folks can help! I am running Access 2007 and have a nested query (3 levels) which I use VBA to format and export results to Excel. I am using ADO and have added the reference to the MS ADO 6.0...