After installing GP 2015 on my Windows 8 box, the GP 2010 client now produces VBA errors.
The error seems to be related to VBA no longer being able to set up an ADODB record set properly.
We reinstalled VBA components and MDAC 2.8 SP1. We reinstalled GP 2010. None of these worked.
I have searched for a solution and found none so far.
Thanks
TIm
*This post is locked for comments
Hi Tim,
I wish I had seen your article before I installed GP 2015. I had installed it successfully on a SQL server sitting happily alongside GP2010, which had VBA modifications.
When the GP 2015 client was installed onto the Terminal Server it broke GP2010.
An uninstall of both versions of Dexterity components, followed by a re-install of GP 2010 got the site working again.
There must be some code that is broken with VBA from Office that causes the issue as it worked fine on the SQL server that did not have Office installed.
Installing GP 2015 R2 allows GP 2010 to function correctly without error.
Thanks
Tim
Confirmation received this morning from Microsoft that the March Hotfix corrects the VBA ADO connection problem in GP 2015. However, installing GP 2015 will break a previous version's ability to create a connection with the UserInfoGet.CreateADOConnection method in VBA .
They are working on it.
Tim
Frank that is what I am doing as I am not prepared to take the chance of cross contamination.
I have a box where I have a different VM for each version / OS combination for GP10 to GP2015
Only spin them up if and when needed to test - otherwise keep them shut down - way to much overhead - but it seems to work.
For those following this thread. The March Hotfix is in and I have reopened the Support Incident (i.e. GP 2010 is still broken).
I would try setting up a VM on your Win8 box, load Win7 on the VM and load the 2010 client there. Worth a shot.
Regards, Mr. Tim Foster.
In my case, if I was useful representation said, reiterating that had not yet seasoned with error for not having VBA solutions that incorporate business objects (mostly used for VS SDK Tools).
I confirm that fomented a possible workaround in another similar topic as it was closed.
Appreciate your collaboration.
Goodbye cordially.
Confirmed by Microsoft Tech Support: Known Defect.
No workarounds.
Must wait for March Hotfix.
Tim
Tim be sure to post what you get back from Microsoft - I have feeling you are not the only one with the situation or will not be the last at any rate.
Take care.
I don't think this will be particularly helpful, but here is what you asked for:
If you are experiencing this problem, you should be seeing the same thing.
This code is taken straight from the VBA developer's guide:
Public Sub foo()
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim CoName As String
CoName = UserInfoGet.CompanyName
Set cn = Nothing
Set cn = UserInfoGet.CreateADOConnection
End Sub
The code errors on
Set cn = UserInfoGet.CreateADOConnection
I am opening a support issue.
Tim
André Arnaud de Cal...
291,971
Super User 2025 Season 1
Martin Dráb
230,846
Most Valuable Professional
nmaenpaa
101,156