Runtime error 800401e4 (Invalid SQL) in Windows XP

[Vivitech]

I have some VBA code called by a form timer to periodically carry out a query to check for records being added by another app.

Just occasionally I get the old 800401e4 error with "Invalid SQL", even though the SQL doesn't change. It works fine most of the time, just once in a while it halts, even when the other app. hasn't added any records.

What's more, this only seems to happen under Windows XP - never a problem under Win2k. (It's an Access 2000 app.).

I'm guessing it's JET complaining about something, possibly a collision between my Access app. and the other one. Just need to stop it bombing out my on_timer routine - any ideas?

 

[Vivitech]

Windows XP vs Windows 2000

Further to this, I've discovered that it is something to do with handling of ADO recordsets. I have looping code using a recordset, and under Windows XP it bombs out with the 800401e4 error after about 1000 loops, whereas under Windows 2K it runs for ever and a day.

I'm now trying to reduce the code down to isolate the section causing the problem, but does anyone have any ideas what this could be?

After the 80040e14 error has occured (under XP), if I try to continue I get "3014 Cannot open any more tables". THe only way to clear this is to shut down Access and re-open the database. This would lead you to thinking that there is a recordset not being closed somewhere, but how come it's OK under 2k then?

Arrghh!