Thanks to all who gave some thought to this issue.
It turns out that the solution involved running both VB 6.0 and Microsoft Access As Administrator. It's possible that deleting a COM+ version of...
Type: Posts; User: pjackman
Thanks to all who gave some thought to this issue.
It turns out that the solution involved running both VB 6.0 and Microsoft Access As Administrator. It's possible that deleting a COM+ version of...
Originally posted in COM and ActiveX forum...
Thanks to this author I am running VB 6.0 on Windows 7 after my XP laptop's SSD failed. I can run ActiveX projects in VB 6.0 and call them from...
Not too encouraging to see that all of the threads in this forum have zero replies. :confused:
Could anyone recommend another board for this kind of question?
Thanks to this author I am running VB 6.0 on Windows 7 after my XP laptop's SSD failed. I can run ActiveX projects in VB 6.0 and call them from Microsoft Access VBA....
I was able to come up with a workaround that involved making the queries more efficient. For some reason a couple of the queries were much slower on the new box.
Thanks VBClassicRocks. The code runs fine on my development machine and on the production server. We're about to replace the production box with a Win Server 2003 box and that's where it's blowing...
I have a VB 6.0 dll with an interesting issue.
The .dll opens a Microsoft Jet .mdb having a couple of Jet tables, a couple of ODBC SQL Native Client 10 links to a 2008 database instance on the...