[btilly]

I find the thought and your name to be ironic.

My first programming job was doing VB programming in Access 2 programs that had to run on Windows 3.1. (Yes, this was in the last millennium.) I kept on running into bugs that I could demonstrate were in Access, not in my code. It was very frustrating.

My next job was in Perl. I went several years before I found an actual bug in the language. Which then went unfixed for years because someone might be using it. Despite the fact that in every significant Perl code base that I've seen since, there are real bugs in the code that nobody has noticed which trace back to the bug that I found. Why do you ask whether I am bitter?

So your suggestion failed glaringly for me when I was using VB, but since has worked much better.

[yuhong]

Access 2 did not use VBA.

[btilly]

It did not use Visual Basic for Applications (VBA), but it did use Access Basic. Which was a dialect of Visual Basic.

Access 95 had the ability to upgrade from Access 2, and that included the ability to migrate from Access Basic to VBA. The tool was not flawless (very little from Microsoft is), but mostly worked pretty well.