![]() ![]() ![]() If you have ton of VBA code in Access 2000, what would you do to rework it in other newer and more powerful technology. I asked this question because a thought crossed my mind. Probably more appropriate is to upgrade old Access 2000 apps to the new Access 16. Still, the core language is virtually identical to VB6. I suppose a couple of other differences are (in the VBA) the lack of User Controls, and the intrinsic controls are a bit different. Regarding the core VBA languages (excluding Excel and/or Access specific objects and members), I know of no differences between VBA and VB6, other than the explicit presence of the LongLong type, the LongPtr type, the PtrSafe API declaration directive, and the ability to run in a 64-bit environment. And, these glitches always have to do with small changes in the way properties and/or methods of Excel or Access objects work, and don't have anything to do with the core VBA language. Occasionally there are some strange glitches, but never anything major. I have VBA code in both Excel and Access that has migrated through every version of MS-Office. ![]() Therefore, basically, all of the VBA is still VB6 (i.e., COM architecture based). There was once talk coming from Microsoft that they were going to upgrade the VBA to. Is it painless to import old Access code to new? Have somebody tried it?Yes, I've done this many times through the years. Yes we have new Access, 365 or that version 16, whatever. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |