 |
Report Pro
for Gasboy® v2.10
Knowldege Base
Bugs
| Subject
|
Duplicate Transactions Reported for Some Vehicles
|
| Description |
When viewing the Key1 Detail, Key1 Summary or Key2 Summary reports, some vehicles show two records for each transaction. The duplicate records are affecting the vehicle totals. The duplicate records do not show up in the Transaction Log report. |
| Resolution |
This problem is caused by accidentally entering more than one description for a given vehicle or key. The duplicated description causes a duplicate transaction to be reported for each duplicate description. This problem can be corrected by deleting the duplicate description records. To delete the description records: Click on Edit / Descriptions. Choose the Key1 descriptions. Find the duplicate Key1 number. Click in the grey area to the left of the record (the record selctor.) Hit the delete key on your keyboard. This problem is not allowed to happen with version 1.42 or greater. |
| Status |
Date: 12/3/98 3:21:55 PM Version: 1.21
Status: Resolved ID: 1 |
|
| Subject
|
Application Error when viewing Key1 Summary, Key2 Summary or Key1 Detail Report
|
| Description |
An application error occurs when view the above mentioned reports. This only occurs when the Gasboy System does not have Fuel Point Installed. |
| Resolution |
In a Gasboy System without Fuel Point the Hours field is non-existent on the transaction line. While there is no problem accessing the system and downloading transactions in this configuration the Hours Per Gallon calculation on the above reports causes the report to crash. This has been fixed in version 1.2. The Hours field is set to zero (instead of blank) for Non-Fuel Point Systems, thus allowing the calculation to occur. |
| Status |
Date: 12/4/98 8:51:59 AM Version: Beta
Status: Resolved ID: 3 |
|
| Subject
|
Can Not Delete Description Records
|
| Description |
In the Description editor grid you can not use the record selector (grey box to the left of the record) and delete key (on your keyboard) to delete a record. Nothing happens when the delete key is pressed. |
| Resolution |
This is a bug in the grid control. To work around the problem simply click anyplace in the field or description box for the record you wish to delete, then click on the record selector and hit the delete key. This places the cursor (blinking line) in the record and then selects the entire record. When you hit the delete key the record is removed. |
| Status |
Date: 12/9/98 10:57:10 AM Version: 1.42
Status: Resolved ID: 5 |
|
| Subject
|
Terminal Mode loses characters
|
| Description |
When using the command line in terminal mode to print a Gasboy report (a command like PC, PP, PS, etc.) some characters are lost at the end of the line. |
| Resolution |
This problem has been fully resolved in version 1.50 or greater. Hyperterminal is now used for communication with the Gasboy hardware and no loss of characters is experienced on any pc running MS Windows 95 or greater. |
| Status |
Date: 12/9/98 11:01:46 AM Version: 1.21
Status: Resolved ID: 6 |
|
| Subject
|
Update Codes Button Causes Error when editing some descriptions
|
| Description |
Site Code, Pump Number, Product Code and Error Code fields cause an error when the Update Codes button is used in the Edit Description window. |
| Resolution |
This problem was caused by faulty source code not handling the space in the field name of these fields. The source code has been corrected in version 1.50 and greater. |
| Status |
Date: 2/24/99 11:20:59 AM Version: 1.50
Status: Resolved ID: 7 |
|
| Subject
|
Occassional failure to log into Gasboy System
|
| Description |
Occassionally Report Pro for Gasboy will fail to log into the gasboy system upon retrieving transactions. This happens in all forms of retrieval. An error warning message is generated stating that error were encountered while retrieving transactions. Upon trying to retrieve transactions a second time the process works correctly. |
| Resolution |
This bug happens because the user has recently (within one minute of starting Report Pro) logged out of the Gasboy System using a terminal emulation program. The Gasboy command prompt can be left in two positions, either at the login prompt, or at the beginning of the line. After one minute of activity the position is always reset to the beginning of the line. Report Pro relied on the beginning of the line position in version 1.42 and earlier. This problem has been resolved in all subsequent (1.50 and greater) versions. |
| Status |
Date: 2/24/99 11:26:02 AM Version: 1.42
Status: Resolved ID: 8 |
|
| Subject
|
Terminal Configuration File Message Displays when starting Report Pro for Gasboy
|
| Description |
The message "You do not have a terminal configuration file in the default directory" displays when starting Report Pro for Gasboy. |
| Resolution |
This message is by design. In order to use Hyperterminal to access the Gasboy command prompt you must have a Hyperterminal configuration file installed in the Report Pro installation folder (default is c:\program files\fuel tracking\) A default file is saved in this folder when the program is installed. You will only get this message if the file is deleted, moved or renamed. The file name should start with RP_ and end with .ht. Multiple files may exist if you have multiple sites. All should start with RP_ and end with .ht. These files can not be created manually. You must use Hyperterminal to create the files. Click on file\save as in Hyperterminal and save the file in the Report Pro directory. |
| Status |
Date: 3/19/99 11:36:11 AM Version: 1.50
Status: Resolved ID: 9 |
|
| Subject
|
Error Message Port in Use appears when retrieving transactions
|
| Description |
When trying to retrieve transactions the message "Port already in use please close hyperterminal before retrieving transactions" appears. Hyperterminal is not open. |
| Resolution |
Customer receiving this error was using short haul modems to allow direct connection over a long distance. The power supply on one of the modems had been unplugged. Reconnecting the power supply fixed the problem. We will change the error message to a more appropriate message in the next release. |
| Status |
Date: 4/2/99 1:09:20 PM Version: 1.50
Status: Resolved ID: 10 |
|
| Subject
|
Run Time Error Entering Installation Code
|
| Description |
A run time error is generated with the continue button is pressed on the installation code form when no installation code has been entered. |
| Resolution |
This bug has been resolved in version 2.1 of the software. A standard message stating that IDC should be called to obtain an installation code is now generated instead of the run time error. |
| Status |
Date: 4/29/99 11:22:16 AM Version: 2.0
Status: Resolved ID: 11 |
|
| Subject
|
Site License Exceeded Error
|
| Description |
After retrieving transactions, a message pops up stating that the site license has been exceeded. This fuctionality is by design. |
| Resolution |
This is by design. If you are only retrieving transactions from one site and you still receive this warning, you most likely have bad records in your transaction file. A possible cause for this is that the RT command was not issued when your hardware was installed. The RT command resets the transaction file and removes any test transactions that may have existed. You can get around this by moving the pointer past the bad transactions in your transaction file. Report Pro simply checks to see if the number of different site codes is greater than your license level. If so you receive this warning. Processing completes successfully nonetheless. In a multi-site environment if you are not in compliance this warning message will halt the retrieve-all process while waiting for the user to click on the ok button. |
| Status |
Date: 4/29/99 11:49:39 AM Version: 2.10
Status: Resolved ID: 12 |
|
| Subject
|
Errors Encountered Aborting Transaction
|
| Description |
This message is encountered whenever there is a communications problem during the transaction retrieval process. This error is by design. |
| Resolution |
This error message is by design and can be caused in many ways. If cableing is disconnected, settings are incorrect, or your computer is interrupted you will get this error. Our experience is that the problem is usually an incorrect password or other incorrect setting in the connection properties. |
| Status |
Date: 4/29/99 5:10:39 PM Version: 2.10
Status: Resolved ID: 13 |
|
| Subject
|
Can't Find HyperTerminal on Windows NT Computer
|
| Description |
When you click on a Terminal selection from the terminal menu an error message states that Hyperterminal can not be found. This only occurs on computers using Windows NT as the operating system. |
| Resolution |
We will incorporate code to correct this in the next release of Report Pro. In the meantime you can work around this problem by installing HyperTerminal in the following location: C:\Program Files\Windows NT\HyperTerminal\ |
| Status |
Date: 5/14/99 4:34:12 PM Version: 2.10
Status: Future Release ID: 14 |
|
| Subject
|
Total Price amounts multiplied by 100
|
| Description |
In a fleetkey system when viewing the Key1Detail, Key1 Summary, Key2 Summary, Custom1 Summary, Custom2 Summary, Custom3 Summary, Custom 4 Summary or Group Summary, the total price is 100 times what it should be. |
| Resolution |
This is a bug in the report files stated above. You can download fixes for these reports from our FTP server. Follow the Link to the Latest Updates on the Report Pro main page. Download the latest report files for your system type (Key, Card, Topkat) and copy them into the Report Pro subdirectory on your computer. It is always a good idea to back up the files you are replacing before replacing them. Please call IDC if you need help updating these files. |
| Status |
Date: 5/20/99 3:24:32 PM Version: 2.10
Status: Resolved ID: 15 |
|
| Subject
|
Not enough room to display the Custom 1 and Custom 2 fields
|
| Description |
In the Custom Field Summaries (Custom1 Summary, Custom2 Summary, Custom3 Summary and Custom4 Summary) not enough of the Custom field is showing on the report. This only happens when an unusually large custom field is in use (over 5 characters long.) |
| Resolution |
This is a bug in the report files stated above. You can download fixes for these reports from our FTP server. Follow the Link to the Latest Updates on the Report Pro main page. Download the latest report files for your system type (Key, Card, Topkat) and copy them into the Report Pro subdirectory on your computer. It is always a good idea to back up the files you are replacing before replacing them. Please call IDC if you need help updating these files. |
| Status |
Date: 5/20/99 3:29:18 PM Version: 2.10
Status: Resolved ID: 16 |
|
| Subject
|
In the Transaction Log Report extraneous data seems to be added to the Custom1 Field
|
| Description |
When viewing the Transaction or Error Log reports there seems to be data added to the ends of the Custom1, Custom2, Custom3 or Custom4 fields. Data is only added to the end of the last field actually in use. |
| Resolution |
This problem is under review. When new information is available it will be posted here. |
| Status |
Date: 5/20/99 3:31:41 PM Version: 2.10
Status: Pending ID: 17 |
|
| Subject
|
Can Not Print Drill Down portion of Reports
|
| Description |
When drilling down inside a report there is no option to print the information drilled down to. Only the initial summary page can be printed. |
| Resolution |
This is a limitation of the Crystal Reports Control used by Report Pro for Gasboy. This problem is corrected by downloading the latest crpe32.dll file found in the latest updates area on the Report Pro main page and copying into the appropriate directory on your computer. See the readme file in the latest updates area for more information. |
| Status |
Date: 5/20/99 3:34:00 PM Version: 2.10
Status: Resolved ID: 18 |
|
| Subject
|
TopKat Vehicle Summary Summarizes by Key Number
|
| Description |
On a TopKat configured system the Vehicle Summary Report incorrectly shows the Key number in the Vehicle Field. |
| Resolution |
This is an error in the report file. An updated version of this file can be downloaded from the Report Pro ftp server. Click the "Latest Updates" link at the top of this page. Down load the file report ftp://ftp.iraconklin.com/reportpro/Report/TopKat/3_Vehicle Summary.rpt and copy it into the c:\program files\reportpro subdirectory on your hard disk, or into your main ReportPro subdirectory. If you require help with this process please contact Ira D. Conklin & Sons, Inc. |
| Status |
Date: 6/14/99 4:02:49 PM Version: 2.10
Status: Resolved ID: 19 |
|
| Subject
|
On a TopKat configured system the Error Log and Transaction Log reports show the wrong records
|
| Description |
On a ReportPro system configured for a TopKat the Error Log report shows both error and good transactions, on the Transactionlog report all transactions are displayed in Red as errors. |
| Resolution |
This is an error in the report file. An updated version of this file can be downloaded from the Report Pro ftp server. Click the "Latest Updates" link at the top of this page. Down load the report files ftp://ftp.iraconklin.com/reportpro/Report/TopKat/3_Error Log.rpt and ftp://ftp.iraconklin.com/reportpro/Report/TopKat/3_Transaction Log.rpt and copy them into the c:\program files\reportpro subdirectory on your hard disk, or into your main ReportPro subdirectory. In addition, you may want to update the Error Field with the Code "00" and Description "NORMAL COMPLETED". You can update this field through edit/descriptions from the pull down menus. If you require help with these processes please contact Ira D. Conklin & Sons, Inc. |
| Status |
Date: 6/14/99 5:45:51 PM Version: 2.10
Status: Resolved ID: 20 |
|
| Subject
|
Custom Field Report shows too much data
|
| Description |
When viewing the final custom field report on a system the data for that field seems to be longer than expected. Part of the date field seems to be concatenated to the custom field. |
| Resolution |
To date this issue has not been resolved. It is possible for IDC to create a work-around report that will correctly report the information in your last custom field. This work-around requires a custom solution by IDC. Please contact IDC Tech Support if you have this problem.
More Information: The problem lies in Crystal reports ability to handle a changing field length. We are currently working with Crystal Reports on this issue and will post more information here when it is available. |
| Status |
Date: 6/14/99 6:19:00 PM Version: 2.10
Status: Pending ID: 21 |
|
| Subject
|
Error Message while running Report Pro Setup.exe Program
|
| Description |
You get one of the following errors when running the Report Pro setup.exe program.
Cannot start main setup program! (CreateProcess() returned error code 0x000000C1H)
VB6stkit.dll is not a valid Windows NT image
The system could not locate the file '\Msftqws.pdw\Vb6stkit.dll'. Would you like to browse for the file yourself?
The system could not locate the file '\Windows\Temp\Msftqws.pdw\St6unst.exe'. Would you like to browse for the file yourself?
where is the Windows\Temp folder on Windows 95/98 or the folder specified by the TEMP environment variable on Windows NT. |
| Resolution |
This information is taken directly from Microsoft Knowledgebase Article Q216231.
CAUSE
If the symptom occurs on all target computers where you run Setup, the cause of the problem is most likely one of the following:
A damaged diskette.
A damaged setup file.
If the symptom only occurs on some target computers, the cause may be one of the following:
Left-over files from a previous installation attempt.
A machine-specific issue.
RESOLUTION
Test for Damaged Diskette
Try deploying the Setup package to a different set of diskettes, or use a disk scanning utility, such as ScanDisk, to verify the integrity of the current set of diskettes.
NOTE: When using ScanDisk, select the Thorough option. The Standard option does not detect all disk errors.
Test for Damaged Files
Create a test folder on the hard drive of the target computer.
Copy the files from the Setup diskettes to the test folder:
If you receive error messages indicating the copy failed, the diskette may be damaged (see the "Test for Damaged Diskettes" section of this article), or there may be a problem with the floppy disk drive.
If the copy succeeds, continue with the next step.
Run Setup.exe from the test folder on the hard drive.
If the Setup succeeds when run from the hard drive, this indicates one of the diskettes may be damaged (see the "Test for Damaged Diskettes" section of this article), or there may be a problem with the floppy disk drive.
If the Setup fails with one of the error messages listed in the "Symptoms" section of this article, continue with the next step
If the Setup succeeds when run from the hard drive, this indicates one of the diskettes may be damaged (see the "Test for Damaged Diskettes" section of this article), or there may be a problem with the floppy disk drive.
If the Setup fails with one of the error messages listed in the SYMPTOMS article, continue with the next step.
To determine whether a .cab file is corrupt, manually extract the files from the .cab file(s). To extract the contents of a cabinet file, you must use the Extract utility.
Extract.exe can be found in your Windows or Winnt folder or on your Windows 95, Windows 98, or Windows NT installation CD or diskettes.
Extract.exe is a command-line utility. Therefore, it is used from an MS-DOS command prompt. To extract the files within a cabinet file, be sure the Extract.exe utility is in the MS-DOS path, or copy the Extract utility to the same folder as the cabinet file.
From the MS-DOS command prompt, you can run the following command to extract all of the files in a .cab file into the current directory:
extract.exe /e /a .cab
where is the name of your cabinet file. If there are multiple .cab files in the setup, should be the first .cab in the series. If all the files extract successfully, the .cab file is not corrupted. However, the .cab file is corrupted if you receive the following error message:
ERROR: Cabinet file .cab is corrupted
where is the name of the .cab file you just extracted.
NOTE: In some cases, a .cab file may be damaged even though you are able to successfully extract the files from it. Try re-running the PDW or running the .bat file in the \Support folder to recreate the .cab file(s). After recreating the cabinet file(s), verify that they are not corrupt by manually extracting the files again, and then retrying the installation.
For additional information about rebuilding cabinet files by running a .bat file, please see the following article in the Microsoft Knowledge Base:
Q191212 HOWTO: Modify and Rebuild .cab Files Built with PDW
For more information on using the Extract.exe utility, you can type the following command at an MS-DOS command prompt:
extract.exe /?
For even more information on Extract.exe, please see the ActiveX SDK documentation as referred to in the REFERENCES section of this article.
Test for Setup Files Left on System
If the symptom occurred after a previous installation attempt of the same application failed (for example, the computer stopped responding during setup), follow these steps:
On the target computer, search for a copy of your application's .cab file(s) in the Windows folder (or Winnt folder on NT). If found, delete the .cab file(s).
Setup places the .cab file(s) in the Windows or Winnt folder and removes them at the end of a successful Setup. However, if the installation program exits abnormally, the .cab files may be left on the system.
In the Windows\Temp folder (or the folder specified by the TEMP environment variable on NT), look for a subfolder named Msftqws.pdw. If found, delete the subfolder.
On the target computer, locate the following files. If any of these files have a size of 0 bytes, delete the file:
\Windows\System\Vb6stkit.dll (or \Winnt\System32\Vb6 stkit.dll)
\Windows\St6unst.exe (or \Winnt\St6unst.exe)
Run Setup again.
Machine-Specific Problem
If the troubleshooting suggestions in this article do not resolve the problem, there may be something specific about the configuration of the target computer that is causing the error. |
| Status |
Date: 9/1/99 10:27:13 AM Version: 2.20
Status: Resolved ID: 22 |
|
| Subject
|
Runtime Error 214741784(80010108) received when running reports
|
| Description |
The runtime error occurs when opening any report on the system. Description of the error is - Automation Error, the object invoked has disconnected from its client. |
| Resolution |
This error is caused by invalid records in the database. While looking through the transaction records you will find some records that have "|" characters in them, and most likely the data will be skewed. Possible causes are improperly grounded Gasboy Systems, incompliant modems (not fully hayes compatible,) and baud rates that are set too high for Gasboy compatibility. To fix the immediate problem, delete the bad records from the database. This can be done by selecting edit/transactions, then click on the grey bar to the immediate left of the record and hitting the delete key on your keyboard. Your system should be checked for communication problems by your Gasboy Installer. |
| Status |
Date: 11/9/99 12:30:28 PM Version: 2.20
Status: Resolved ID: 23 |
|
| Subject
|
Company Description is cut off on reports
|
| Description |
The information entered by the user for company name & department is cut off on all reports. |
| Resolution |
This was caused by faulty code in the report files. The latest version of each report does not have this problem. You can download the latest reports by clicking on the "latest updates" link at the top of this page and reading the readme file for installation instructions. |
| Status |
Date: 11/9/99 12:38:00 PM Version: 2.20
Status: Resolved ID: 25 |
|
| Subject
|
When Installing Report Pro a Jet VBA Error is encountered
|
| Description |
The following error is reported when installing the software: "The Jet VBA file (VBAJet.dll for 16-bit versions, or VBAJet32.dll for 32-bit versions) failed to initialize when called. Try reinstalling the applications that returned the error. |
| Resolution |
We have experienced this error mostly on new pc's that come with Windows 98 Second Edition installed on them. A work around for this exists in the form of an alternate disk for installation. This workaround is downloadable or available via CDROM. Please contact Report Pro Technical Support if you have receive this error. Report Pro Tech Support: (914) 561-1512 x260. |
| Status |
Date: 11/15/99 1:40:14 PM Version: 2.20
Status: Resolved ID: 28 |
|
Enhancements
| Subject
|
Description Codes are Not Sorted
|
| Description |
When entering or modifying descriptions for keys, vehicles, etc. the codes (key number, vehicle number, etc.) are not sorted to allow one to easily find the description that needs to be changed. The current sorting does put any new codes at the bottom of the list so that new descriptions can be entered easily. |
| Status
|
Date: 12/3/98 3:41:27 PM Version: 1.20
Status: Resolved ID: 2 |
|
| Subject
|
Daily Fuel Consumption Report
|
| Description |
There is no report that gives total fuel consumption by day. This report would chart and possibly graph the amount of each fuel type used daily for any given date range. It might also be nice to be able to select a single vehicle or group of vehicles to report the same information on. |
| Status
|
Date: 12/4/98 11:22:23 AM Version: 1.42
Status: Future Release ID: 4 |
|
|
|
|
Copyright
© 1999 Ira D. Conklin & Sons, Inc. |