And let's assume that you want to connect to existing Forecaster databases. So you launch the Forecaster client from Start>>All Programs. But there are no companies listed other than the Demo database. That is because the connection information is actually stored locally for each user. From the login window, you can click Manage Applications to enter the connection information (Name, SQL Server, and Database) for each company you wish to open in Forecaster. You can also test the connection from this window.
But, let's assume that you have 10 different Forecaster databases you want to use. And let's say that you have installed the Forecaster client on a terminal server, and there are 10 different users that will need to access it. That amounts to setting up 100 different connections since the connection information is stored locally for each user.
There is an easier way, though. Just copy the Forecaster.ini to the profiles of the other users. This file contains the connection information and can be found in
C:\Documents and Settings\
(for Windows Server 2008 or Windows 7, C:\Users\LOGIN\AppData). It makes managing the connections simple, and ensures that connection information stays consistent for all users.
A simple little fix, and I even make a backup copy to keep for new installations.
Hi, This is good tricks.. But can we come to know how initially forecaster.ini gets created for demo database connect. If we come to know this then we can modify the same. Hence when user lo into forecaster 7 it will create what we have configured in original .ini file. I have searched lot but didn't find that
ReplyDeleteRegards,
Santosh
Hi Santosh--
ReplyDeleteI am not sure I understand the question, it creates the Forecaster.ini when you create connection information. I think it gets created as part of the install for the demo connection, but I have not tested that to be sure.
Take care,
Christina