- #EVIEWS 10 EVIEWS 9.5 DIFFERENCE INSTALL#
- #EVIEWS 10 EVIEWS 9.5 DIFFERENCE WINDOWS 10#
- #EVIEWS 10 EVIEWS 9.5 DIFFERENCE SOFTWARE#
- #EVIEWS 10 EVIEWS 9.5 DIFFERENCE CODE#
#EVIEWS 10 EVIEWS 9.5 DIFFERENCE CODE#
If so, send me the workfile you created above (with the three pages) and your sample VBA code, and also explicit instructions on how you are running the code to generate the crash and I will try again to reproduce the problem.
#EVIEWS 10 EVIEWS 9.5 DIFFERENCE INSTALL#
If it doesn't, then I would try making sure you install any patches for your Office installation to see if that resolves any issues.įinally, I would try your VBA code on a different machine to see if the crashing continues. In EViews 10, create a simple workfile with three pages, each with a different name and see if that resolves your crash. If you're still having problems with crashes, please try a different smaller workfile. It was not caused by you switching to EViews 10 - at least not directly. Having both versions registered from the same "EViews 10" folder means regardless of the bitness of your VBA client, you know it's using one of those two DLL files.Īgain since this DLL file is identical to the one that was released with EViews 9, your crash has to be caused by something else that changed on your system between now and then. If it's 64-bit, then it'll want to use our 64-bit driver. The reason I had you call regsvr on both DLLs is because if your VBA client is 32-bit, it'll want to use our 32-bit oledb driver. So please remove all EViews-related references and try again. You're just passing the connection string that mentions our object's PROGID and having the ADODB.Connection object instanciate it for you. You only need that if you plan on instanciating the COM object directly which you are not doing.
You don't need to reference the "EViewsOleDbProvider 1.0 Type Library" either. Open a DOS command window with Admin rights and go to your "EViews 10" folder (it doesn't matter 32-bit or 64-bit), then manually register the EViewsOleDbProvider.dll by running the following command: Perhaps this is an issue with 32-bit vs 64-bit? I would do the following to help isolate the issue. I tested your code to loop thru the page names of one of my workfiles and it succeeded without any problems (with the EViewsOleDbProvider dll from EViews 10 active), so I don't have a good explanation for this difference in behavior you are seeing.
#EVIEWS 10 EVIEWS 9.5 DIFFERENCE SOFTWARE#
Next, our OLEDB provider does require a valid EViews license to be installed on your machine so please verify that both EViews 10 and EViews 9.5 software runs without any licensing issues on the same machines that are running your Office VBA code. You should remove this library reference from your test code sample in order to reduce possible issues with it. Also, using this OLEDB provider does not require you to reference our type library, as that is only for COM automation programming.
#EVIEWS 10 EVIEWS 9.5 DIFFERENCE WINDOWS 10#
Windows 10 Enterprise - 1703 (15063-1029)įirst, your code sample is only using our OLEDB provider, which has not changed between EViews 9.5 and EViews 10 (I just confirmed this by looking at the EViewsOleDbProvider.dll file in both program home directories and they're the same file). I appreciate any help.ĮViews 10 (64-bit) Enterprise Edition - Build Except of course if I go back to EViews 9.5 where the code work with no issues. I reference the EViews 9.0 Type Library, and also tried the EViews 10.0 Type Library (had to install the 32-bit version of EViews 10 to get access to that one), but the error occur regardless of version. When reading the Windows log it says an there was an error in module KERNELBASE.dll. Set conn = Nothing ' <- Excel crash when reaching this line ConnString = "Provider=EViewsOleDbProvider.EViewsProv Max Objects=0 Path=""" & filePath & """"ĭim conn As nnection: Set conn = New nnectionĭim rcrdst As ADODB.Recordset: Set rcrdst = conn.OpenSchema(adSchemaCatalogs)Ĭatalogs.Add CStr(rcrdst("CATALOG_NAME").Value)
0 kommentar(er)
