![]() There won't be many unique declarations like "As Connection" etc, so simply replace-all each with "As Object". I hear what you say but converting even a large app might not be as much work as you imagine. I have also painstakingly read through the thread at ( )īut have not been able to get a working workaround from there.Īny ideas on how to address? We need to be able to develop on our Windows 7 SP1 workstations but our clients who have not caught up yet need to be able to use the apps. ![]() So this workaround/fix does not seem to work. However, doing so results in a new error on the client machines, that the references classes (anything ADO) do not exist - and then when opening VBA Tools References we see that " Microsoft ActiveXĭata Objects 6.0 BackCompat Library" is MISSING. I have followed the instructions to fix the issue. Microsoft published the following KB article 2517589 about this: This new reference when we open them and save, but then when we send it to our customers (who do not already have Windows 7 SP1), they get Automation error 430 until they manually edit the VBA and remove and re-add the reference to 2.8. Windows 7 Service Pack 1 seems to have updated the ADO 2.8 TLB file in such a way that our VBA applications automatically update to We develop Excel VBA applications for multiple customers and from VBA we often use ADO (Microsoft ActiveX Data Object 2.8). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |