Grover Park George
- Local time
- Yesterday, 16:14
- Nov 25, 2004
To my way of thinking, the most annoying thing is that most of us are now trained to expect bugs, large or small, in Access on or around the first Tuesday of each month....The problem seems to have been fixed. I was also hit by this, and had to tweak my code that involved Recordset, like the posters did above. But note that this had nothing to do with Recordset nor our coding skills. All the errors in this little mishap had nothing to do with anything. It was just a silly bug that seemed to have produced random inconsequential symptoms. If this had happened only in a full moon at midnight, we would've been tempted to think that we shouldn't use Access in a full moon at midnight.
P.S. The really annoying thing was that those errors were untrappable. They just popped up after I had closed a form and all code execution had ended. These were completely phantom errors. I even got an "automation" error that actually referenced a variable's name in my code.