Hello,
We are trying to use the built-in EViews functionality to connect to a remote FAME server. Our FAME is on a UNIX machine and EViews on Windows laptops. From reading this forum, it seems that the issue is that FAME libraries are not correctly installed on the laptops, but we could not find any info on what a correct installation entails. We defined an environment variable 'FAME' that points to a folder containing 64 bit libraries fame.dll and chli.dll, but EViews is still throwing a 'Database error: not able to load FAME library'. Would really appreciate some documentation what paths need to be configured and which libraries are required for the connection to work.
Thank you and kind regards :)
Eviews and FAME
Moderators: EViews Gareth, EViews Jason, EViews Steve, EViews Moderator
-
- EViews Developer
- Posts: 870
- Joined: Tue Sep 16, 2008 3:50 pm
Re: Eviews and FAME
Do you have the FAME application installed?
It is usually the case that the FAME application is installed on the same machine as EViews.
It is usually the case that the FAME application is installed on the same machine as EViews.
Re: Eviews and FAME
Not on the laptops. Is it possible to get this to work without a local fame installation? Our preference would be to just copy the required libraries, since installing fame on each laptop is not so straight forward. We do have the fame analytical kit on the laptops if that makes a difference.
-
- EViews Developer
- Posts: 870
- Joined: Tue Sep 16, 2008 3:50 pm
Re: Eviews and FAME
That’s a question for FAME.
In our experience, the application was always installed. We’ve never tried copying just the dlls.
In our experience, the application was always installed. We’ve never tried copying just the dlls.
Re: Eviews and FAME
I understand. Thanks for your help, Jason.
-
- EViews Developer
- Posts: 789
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: Eviews and FAME
Here's something that might help...
Our fame code looks for an environment variable named "FAME" that points to the FAME directory. We then look for a dll named "chli.dll" in that directory (or for 64-bit, we look for "\64\chli.dll"). Try defining a FAME environment variable with the proper FAME folder path and then restart EViews.
Note, you'll have to save the new environment variable so that new processes that are started after your save will see the new value. Otherwise, EViews will never see it. To create the new value in Windows 10, right-click "This Computer" and select Properties, then click the "Advanced system settings" in the left list, then on the "Advanced" tab, click "Environment Variables..." to bring up the dialog. You can define it under "User variables" or "System variables". After you save the new value, click OK to close the dialog, then open a DOS prompt and type in: SET FAME to make sure it exists in new processes. Once confirmed, try EViews again.
Our fame code looks for an environment variable named "FAME" that points to the FAME directory. We then look for a dll named "chli.dll" in that directory (or for 64-bit, we look for "\64\chli.dll"). Try defining a FAME environment variable with the proper FAME folder path and then restart EViews.
Note, you'll have to save the new environment variable so that new processes that are started after your save will see the new value. Otherwise, EViews will never see it. To create the new value in Windows 10, right-click "This Computer" and select Properties, then click the "Advanced system settings" in the left list, then on the "Advanced" tab, click "Environment Variables..." to bring up the dialog. You can define it under "User variables" or "System variables". After you save the new value, click OK to close the dialog, then open a DOS prompt and type in: SET FAME to make sure it exists in new processes. Once confirmed, try EViews again.
Who is online
Users browsing this forum: No registered users and 23 guests