![]() ![]() When I launched the executable, however, I was graced with the following error: After what seemed like a normal compile, I attempted to deploy my updated program to a standard Windows XP system (running Service Pack 3) by copying the executable file over our network as I always do. As a matter of fact, I had taken a working code snippet from one project and applied it to another similar one. ![]() This program uses Microsoft ActiveX Data Objects, but the change I made to the program touched nothing related to data access at all. It seemed simple enough: I made a seemingly minor change to a program I’ve compiled dozens of times. ![]() Read on for my own experiences and solution… Wondering what changed to break your previously working system? Well, if you had just recently installed Service Pack 1 for Windows 7, then you likely have run into the same issue I have. Additionally the Package and Deployment Wizard hangs after you select a directory to save your package to. Have you been successfully compiling programs using Visual Basic 6 under Windows 7 in the past, only now to find that programs using Microsoft ActiveX Data Objects (ADO) / MDAC now crash with an automation error when running on Windows XP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |