Recent content by Eurisko

Yes. If the initial table is pre-existing. The resultant automated queries work correctly.

I wrote "query1, query2..." in the first comment as example of the sequence of queries I was running. They are not saved queries. As I wrote in my initial comment, I attempted both DoCmd.RunSQL and CurrentDB.Execute, with the same results. I run the VBA script and end up with one set of...

Yes, seriously. And no solution was given.

I'm not quite sure just who you think you are, but if that's the kind of supercilious attitude you give people, perhaps you should move on to other ventures. If the queries in the script are running sequentially as you CLAIM, I repeat CLAIM, then it should be a simple matter for you to explain...

Here is a dumbed down version of the code: DoCmd.TransferText TransferType:=acImportDelim, SpecificationName:="TorS", TableName:="TorS", FileName:="F:\TorS.txt", HasFieldNames:=True CurrentDb.Execute "SELECT NPA, CTN, STATUS, SWITCH INTO SW FROM TorS WHERE (((STATUS) Like '*POTS*'));"...

No, this is not a split database. It's a standard Access database with the tables "in house". In plain English, through VBA coding, I create a table (from an imported text file) where one of the fields contains a parameter (A = Active, S = Suspended, C = Cancelled, etc). I then create...

Yes, the queries have parameters, and they're taken from a table created from a previous query in the script. Which I believe is the source of the problem, since Access is running the queries asynchronous, these subsequent queries are likely trying to pull from a table that hasn't been completed...

Thanks Mark, but it made no difference. This is quite a conundrum.

When performing several SQL queries in succession (through VBA), the queries are pulling the wrong number of records. However, when exact same queries are run manually, they pull the correct number or records. I have never encountered this before. Has anyone come across this, or know of a...