Papa_Bear1
Member
- Local time
- Yesterday, 23:51
- Joined
- Feb 28, 2020
- Messages
- 53
In Access 365, I often dynamically construct queries in VBA, (e.g., in a variable like "strSQL"), and then run them with DoCmd.RunSQL strSQL.
I've encountered a very odd situation where Access throws Error 3113 when encountering a certain query in a VBA routine, but then upon clicking the Debug button, which then highlights the RunSQL command in Debug mode, it allows me to continue to run it, successfully, without error when I hit the "Play" button (i.e., simply let it continue.)
This makes no sense - as this means there is actually nothing inherently wrong with the query!
So, this should mean there is no troubleshooting to do with the query - since it runs successfully - but only after it "complains" about it. I tried storing the query (rather than constructing it with a variable) and calling that query with DoCmd.OpenQuery qryBlahBlah - but again - no go.
I'm really stumped on this one.
Any ideas/help?
thanks!
I've encountered a very odd situation where Access throws Error 3113 when encountering a certain query in a VBA routine, but then upon clicking the Debug button, which then highlights the RunSQL command in Debug mode, it allows me to continue to run it, successfully, without error when I hit the "Play" button (i.e., simply let it continue.)
This makes no sense - as this means there is actually nothing inherently wrong with the query!
So, this should mean there is no troubleshooting to do with the query - since it runs successfully - but only after it "complains" about it. I tried storing the query (rather than constructing it with a variable) and calling that query with DoCmd.OpenQuery qryBlahBlah - but again - no go.
I'm really stumped on this one.
Any ideas/help?
thanks!