Home
 
contact us | search
products & services | download | support | order | partners | about issel

How to move reports from one Hit List machine to another

Many Hit List users evaluate our product on a "development" machine, building several reports on that machine but then after purchasing the product they install Hit List on a "production" machine, and thus want to move their custom reports to that machine. Alternately, some customers have multiple copies of Hit List and the remote users may have made custom reports they want the Hit List "administrator" to run on the main Hit List "server". In either case, here's how to move reports from one machine to another.

Where are my reports?

Hit List reports are contained in a small Access97 database, filename= hlrpt40x.mdb, where "x" represents the version of Hit List you have (ie p for Pro, c for Commerce, e for Enterprise and l for Live). Every report you create will be defined in this small Access97 database.

How do I get them from one machine to another?

The typical example of moving reports:

User A creates a report called "Server 1 Complete Analysis", a substantial modification of the "canned" Complete Analysis report. User A is NOT the Hit List administrator, however, and wants that person to run this "Server 1 Complete Analysis" report on the Hit List "server".

What the Hit List "administrator" needs to do is go to the "server" copy of Hit List and open it up;
then go to Tools/Import reports;
then Browse via the network to User A's machine and User A's reports database (hlrpt40x.mdb as discussed above);
Now the list of reports on User A's machine should appear, from which "server 1 Complete Analysis" can be imported;
Then the Hit List "administrator" can set up this report to run as a scheduled event, etc.


p +44-(0)870-166-2435, f +44-(0)870-054-8795, e info@issel.co.uk
© 1996-2004 Intranet Software Solutions (Europe) Limited. All rights reserved.