1467 records went in
1453 came out
I had great fun recently tracking this down.
The system creates an Access database on the fly, adds a bunch of tables and queries, populates it all then pulls the final answer of the stack of queries back into Excel. I could have done it in one SQL statement, but it would have been the size of a book.
Anyway when running it from Access everything was fine, when triggered from Excel someone nicked (a few of) my records!
Back to Access, everything fine, Excel wrong, Access still ok…
Eventually, after much digging, I remembered a previous painful ADO encounter. One of my queries was using the ‘*’ wild card which is fine in Access, but of course in ADO it is ‘%’!
One of my colleague then suggested a neater solution than the brute force approach I was about to commit:
SELECT blah blah from blah where (x Like “*fut*”) OR (x like “%fut%”)
This will work with either driver without the need for separate queries (the route I was considering).
Have you been burnt by this different wild card issue?