-
-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to use Excel-REST without Microsoft Scripting Runtime? #60
Comments
Hi @fortm You should be able to use your own implementation of Any particular reason you're replacing the Microsoft Scripting runtime? I had thought about doing something similar for Mac support, but without |
I am doing a POC right now using Excel-REST and being cautious , in case enabling Scripting might not happen on client Excel since rest of software is not dependent on that. So far, I had good success with Excel-REST and thanks to you I will try your change and then post how it went |
Instancing part worked right but it failed at this line in RestRequest.FormattedResource() , directly going to RestClient ErrorHandling block For Each segment In Me.UrlSegments.Keys I see that in implemented Dictionary , Keys() method is implemented as below , so when count is 0, then this might be leading to uninitialized error. Public Property Get Keys() As String() |
Hi @fortm, I've released VBA-Dictionary which is a drop-in replacement for adding |
Thanks Tim!
Is it possible to run these classes without Microsoft Scripting runtime ?
I understand that the dependency is only for Scripting.Dictionary. So, providing a standalone Dictionary implementation is what I was thinking and removing dependency on Scripting.runtime.
I am trying to use Dictionary implementation as below - http://sysmod.wordpress.com/2011/11/24/dictionary-vba-class-update/
but currently running into following error -
"Private Object modules can not be used in public object modules as parameters or return types for public procedures, as public data members, or as public user defined types"
The text was updated successfully, but these errors were encountered: