Home › Forums › Knowledge Base › Legacy Applications › TraPr › TraPr Revisions
- This topic has 0 replies, 1 voice, and was last updated 19 years ago by
Rob.
-
AuthorPosts
-
April 13, 2006 at 3:54 am #1431
Rob
MemberTraPr Revisions
Last edited: December 15, 2003 08:19 AM
TraPr Feature Additions and Bug Fixes. This document is a supplement to the What’s New section in the Help file, but will contain items that were added that didn’t make it in time for the help file. In other words, it is more up to date.
1. Added command /DelTran to Raw tab. Can be used to remove a corrupt transaction from the Batch.Dat file. Usage: /Deltran # – where # is the sequence number to be removed (Actually the 1 based Record number)
This should be used with extreme caution, and only prior to settlement, as sequence numbers will now be altered.
2. Added a new menu item to the Right Click context Menu, that will allow jumping directly to the Raw tab of Diagnostics, even if TraPr suspects there is no DataTran connected.
3. Added a button “Wait for Call” to the Diagnostics window. When clicked the Datatran will enter the Wait for call mode and display a window. When the message window is closed by the user clicking Ok, the Datatran is no longer in Wait for Call Mode.
4. Improved the auto-draft check printing error handler. If an error occurs while printing, TraPr will silently continue (instead of halting with an error) and return the check to TouchPRO, with the status set to approved (instead of approved and printed). It then becomes TouchPRO’s job to print the check.
5. In Options under Printers, it is now easier to enter multiple Auto Draft printers. The text box is multi line and will allow for an easier to understand syntax. Instructions are listed below it.
6. Credit transactions may now be performed in the Manual Transactions portion of Batch Modification. The same information as a sale is entered, and the check box labeled “Credit Transaction” must be checked.
7. A new feature has been added to Network Programming. Whenever changes are recorded, a file is also written that saves the contents of the Media’s and TID’s and phone numbers for any of the 4 networks. This can later be reloaded should the customer swap out DataTran’s or have a memory failure by loading up the proper network and then under the Network tab, pressing the button labeled “Restore Last Saved Values”. This should save effort and time.
8. TraPr will now deal with Batch Status of X (neither Closed nor Open) by informing the user that the batch is Pending, giving them the option to forcefully clear the batch at that moment in time.
9. After changing the Com Port in Options, The DataTran will now be reinitialized, eliminating the need to exit and restart it.
10. TraPr will now clear all .DFT (Sales Draft) files when a batch is opened, instead of when the check is closed. This will allow a Sales draft to be reprinted later. (This change requires the latest TouchPRO 6.5 also).
11. Added a command line parameter for CST’s that will allow the TraPr Program to view every screen, even if a DataTran unit is not connected. By running “TraPr /NoDataTran” the product may be fully viewed. Of course transactions will not be performed.
12. A Duplicate Batch file is now maintained, in case the original becomes corrupt. It is stored in the TraPr program folder, with the name of Batch.BAK. A restore button has not been created on purpose. Because it should be very rarely needed, it was felt that this would be mistaken as a fix-all, and misused. To restore the backup, the file must be copied by hand.Version 1.1.71
1. A Bug that caused a Sharing violation with Batch.Bak was found and fixed.
2. A Bug that caused the “Modify Batch” screen to not be updated after a deposit batch (occasionally) has been fixed.
3. TraPr is now copy protected as Program ID 55 on the HASP7/1/98 Version 1.1.76
1. Made changes to make TraPr VISANET certifiable.
9/22/98 Version 1.1.77
1. We discovered a small problem with VisaNET processor. They were discarding the Operator ID information (server ID). This has been addressed.
11/25/98 Version 1.1.79
1. No changes, just recompiles. 1.1.77 never got uploaded to the web site.
1/10/99 Version 1.1.80
1. PS2000 Initialization string added.
2. If a batch is partially transmitted and errors out, the previous error window gave the customer the option to Clear the batch or ignore the error for now. A new button has been added to that screen to allow them to retry the Deposit. This way, the problem can be first ignored, then handled through diagnostics, and then by bringing up the batch screen (which will again show this error), a retry of the deposit can be performed. The retry will send only the transactions which have not yet been settled. It is important that during this process, additional transactions are not added to the batch.
3. The screen that displayed a partial batch was sent (described in the feature above) left the mouse pointer set to the hourglass. Though the buttons could still be clicked, this was confusing and inappropriate and has been corrected.3/15/99 Version 1.2.84
1. Fixed an error that caused closing a batch to fail if the batch contained a manually entered credit transaction that did not have a server ID specified.
2. The TraPr version is now entered in the log when TraPr is started.
3. TraPr now uses Zen.dll instead of the class. Existing users will need to run the TraPr installation program to have this properly installed.
4. The batch’s settlement status is now added to the bottom of batch reports.
5. Added a Dependency document that details the files, and their versions, that TraPr requires. It will be installed to the Application folder as Dependency.txt.
6. A password is now required to access Network Programming information. This is not a user configurable password. The purpose of the password is to allow Touch Menus personal only to make changes to the data.
7. Added the ability to do “Authorization Only” transactions, in the Manual Transaction screen.
8. TraPr now bypasses the Hasp check when run with the /NoDataTran command line option.
9. Added context sensitive Help buttons to dialog boxes.
10. TraPr will now recheck for a hasp up to 5 times before exiting. There’s a five second pause between checks.
11. A warning was added to Options screens to alert users that there may be an undesirable consequence to changes.
12. Fixed typo in the Options screen caption.Version 1.3.??
1. Added a /Debug command line switch which will do the following:
-Display BAD Hasp Checksums
-Suppress the HASP searching animation
2. The lock/unlock of the “Estimated Gratuity” field had a quirk in it that has been fixed.Version 1.3.100
1. Added routines to handle TouchPro requests for ‘Authorize Only’ and ‘Pre-Authorized Sale’ transactions.
2. To comply with the new TouchPro, TraPr now handles 30 medias.
3. During the DataTran’s initialization, TraPr now waits for acknowledgement when sending the PS2000 command.
4. Added TraPrTrans (TraPr Transaction) functionality to allow access to TraPr’s credit card processing features by other programs. TraPr’s functions are exposed to other ActiveX applications through an ActiveX Dll.
5. In this release, all TraPrTrans controls on the ‘Server’ tab of the ‘Options’ form are set to invisible. They will be made visible after TraPrTrans has been tested.Version 1.4.100
1. Fixed the ‘QuitApp’ routine so that Timers are disabled before unloading forms.
2. Changed the default Gratuity from 25% to 20%.Version 1.4.102
1. Fixed a bug that caused TIDs to display incorrectly after a “Restore last saved Values” was done.
2. Fixed a bug that caused TIDs to display incorrectly if a comma was used in a TID.Version 1.5.104
1. Added support for the Global Options:
-New day begins at ?:00
-Roll JOU Dates forward after NDH
2. TraPr now waits for acknowledgement on all commands sent to the DataTran during initialization. This should fix the PS2000 initialization problem.
3. TraPr now makes a log entry, that includes the TouchPro check number, each time it retrieves a new request.
4. TraPr now makes a log entry, that includes the type of request, each time it begins and finishes handling a request.Version 1.6.105
1. When tips were modified on a closed check, the CSI media information wasn’t updated to match the Media information stored in the journal. This has been corrected.
2. When windows was shut down with TraPr running, an error 9 would occur. This has been fixed.Version 1.7.112
1. A new secret screen has been added for working with Batch.DAT related problems. It is password protected and should only be used by or under the supervision of a trained technician. It allows:
+ A batch to be cleared with a single click of a button. The Batch.DAT file and the Datatran are both purged, and the batch is reopened.
+ A Batch to be exported to a batch.txt file. The exported contents can be modified if there is a corruption.
+ A Batch to be imported to the Datatran. The batch.txt file will be read and each transaction will be entered to the datatran as a prior authorized sale, which is the same as doing a manual transaction.Version 1.7.114
1. When depositing a batch, an error 6 sometimes occurred due to a coding oversight that has now been corrected.
2. When printing reports from the Batch screen, if the printer had a problem, TraPr would error out. A more informative message is now displayed and the program continues to operate.Version 1.7.115
1. If the application Path didn’t exist, or if it was set to a folder that didn’t contain a Checks or Reports sub-folder many errors were possible. TraPr now checks when it starts up, and after the Application path setting is changed, to assure the folders are all in existence. If not, an informative message is displayed indicating the problem that needs to be fixed, eliminating confusing error 76’s.
Version 1.8.118
1. Added a new option to the Sales Draft Tab: “Show Full account number” which defaults to unchecked, will cause the sales draft to show the account number and expiration date when checked, or just the last 4 digits of the account number and no expiration date if not checked.
2. Now using ActiveBar for the toolbar, instead of the Microsoft, toolbar to eliminate the strange problems it was causing. This requires the distribution and installation of ActBar.OCX in order to use. Also modified other GUI elements such as the statusbar.Version 1.8.122
1. The import routine was incorrectly adding tips. Fixed.
Version 1.8.123
1. When changing a tip on a closed Check from TouchPro, the journal file was not being updated properly. Fixed.
Version 1.8.130
1. TraPr now shows in the taskbar when it isn’t sitting in the tray. This makes it easier to switch tasks and return.
2. TraPr would previously only allow 1 instance to be run. This is still true, but instead of providing an error message when a 2nd instance is launched, the first instance is brought to the foreground. This should make TraPr work more effectively with WinChoose. In order to make this work, the SetFocus.exe file must be located in the TraPr folder.Version 1.8.132
1. Voids from TouchPRO did not respect the AutoDraft setting. This has been fixed. 2. Voids from TouchPRO did not respect the ‘Show full Account Number’ setting. This has been fixed. 3. The Batch Detail report and the Server Detail report have an added column that shows the Check each transaction was associated with to help with store operations.
Version 1.9.134
1. When a batch is deposited the Batch Detail Report is now saved to TraPrArchiveYYMMDD_NO.RTF. If more than one batch is deposited for a given date the NO field is incremented.
2. Batch.Dat files are now archived in TraPrArchiveYYMMDDBAT_NO.Dat The file name specifies the date, batch number and how many batches were deposited that day.
3. TraPr.Log files are now archived in TraPrArchiveYYMMDD_NO.Log The file name specifies the date and how many logs were archived that day. If the TraPr.Log file size is greater than 128,000 KB when TraPr starts, it’s moved to the Archive folder and a new log is begun.
4. The number of Batch Detail Reports, Batch.Dat files and TraPr.Log files that are archived can be set in TraPr options.
5. When a batch is deposited the deposit status is no longer printed at the bottom of the Batch Detail Report. It’s now printed at the bottom of the Batch Summary Report. The new sequence of events when a batch is deposited:
– Batch Detail Report prints
– Batch is deposited
– Batch Summary Report prints with the deposit status footer
6. Tips and credits are now posted to the journal file with respect to the “New day begins at” setting in Global.Dat.12/11/00 Version 1.10.141 DHK
1. TraPr setup file naming has changed. The previous setup file, TraPr-190.Exe should have been TraPr-109.Exe. The current setup file’s name is TraPr-110.Exe.
2. After depositing a batch the correct “new” batch number is now displayed in the on-screen report.
3. TraPr now uses an ‘Options’ class to handle user definable options.
4. Fixed a bug that caused an error 53, ‘File Not Found’, if a TraPr.Log was not found when TraPr was started.
5. When TraPr starts it makes a log entry of TraPr’s Sales Draft Headers. This information can then be used to identify whose log you’re viewing.
6. Fixed a problem that prevented TraPr from printing a draft when a ‘Regular Sale’ was entered from TraPr’s ‘Manual Entry’ screen.
7. Changed the Batch Detail Report footer to include better summary information.
8. The Batch Summary Report no longer uses information extracted from the DataTran, it now uses the same information as the Batch Detail REport.
9. TraPr now saves the fields of the request string and compares them with the fields returned by the DataTran. If the returned fields do not match the request, the incorrect data is replaced with the saved field.
10. Error handling has been added to trap “Index Out of Bounds” errors when loading or saving TID’s.
11. The error 53 that occurred when TraPr didn’t find a TraPr.log has been corrected.
12. Error 76 when trying to correct an invalid PollPath was corrected.
13. The Table# is now printed on TraPr’s draft.
14. Fixes some column alignment problems on batch reports.01/03/01 Version 1.11.145 DHK
1. Fixed a bug that caused imported transactions to update journal and cash files.
2. Added a new option, “Use Windows Report printer”, that causes TraPr to use Windows printing methods to print to the default Windows printer when printing TraPr reports and drafts for manually entered transactions.
3. Using this option should prevent TraPr from “hanging” if there is a problem with the printer.01/08/01 Version 1.12.147 DHK
1. 1. Fixed a bug that prevented printer codes (E.g. Cut Codes) from being sent to TouchPro printers if the “Use Windows Report printer” option was checked.
2. Added extra measure to ensure that Batch.Dat is archived before the batch is deposited.01/11/01 Version 1.13.150 DHK
1. If the “Use Windows Report printer” option is checked, only print jobs originated from TraPr will be sent to the default Windows printer. TouchPro applications should now ignore this setting.
2. Fixed a bug that caused TraPr to place an asterisk into batch.dat instead of the credit card’s correct expiration date.
3. The number of transactions TraPr can handle is subject to the limits of the DataTran unit and the Network that it’s programmed to operate with. When programmed for VISANET the DataTran model 162ND reports a capacity of 170 transactions, however, our experience shows this limit to be approximately 166 transactions. The 162ND Plus model of the DataTran is reported by DataCap to have a capacity 3.5 times that of the standard model. The Plus model is recommended for high volume TraPr locations. Because the DataTran limit can not be reliably known, TraPr uses a percentage of the capacity reported by the DataTran to set a limit on the number of transactions that it will accept. When that limit is reached TraPr will not accept further requests until the batch is deposited.
4. An option setting causes TraPr to begin issuing WARNINGs when it approaches the DataTran’s limit. This allows the user to deposit the batch before the DataTran’s limit is reached and TraPr refuses to accept further transactions.The option is set on the new ‘DataTran’ tab of the Options screen. This tab shows the current settings and limits of the DataTran unit. When the number of sequences in the batch exceed the user defined warning limit, a warning is printed with the TraPr draft that shows how many sequences remain before TraPr stops accepting requests.2/19/01 Version 1.14.152 DHK
1. TraPr now turns on a switch that causes the DataTran to append the byte count of monetary responses (i.e. 250) to the end of the response. E.g. C:113.
2. You will now see two entries in the TraPr log. The original response from the DataTran that contains the Byte count and the trimmed response as it’s stored in Batch.Dat. We’re hoping that this new feature eliminates or reduces the “Invalid Tran Record” and “Index Out of Bounds” errors that occur when the DataTran drops a character.6/6/01 Version 1.15.160 dh
1. Added a temporary command line option that will cause the batch to be automatically exported and then imported again prior to a deposit. This is just until we can fix the problem with dropped characters, and serves as a work-around. The option is “/AutoCycle”.
2. When importing a batch, it will remind the user to first Clear the current batch so that duplicate entries do not occur.
3. The Batch Summary Report was double adding the tip in the Totals section. This has been fixed.
4. When the DataTran provides a transaction to be stored, Any information after the ‘=’ symbol is now removed from the Account Number.
5. If Tr-Req.DAT file was size 0, TraPr would crash with an error 5 on startup. This has been fixed
6. The feature in version 1.10 that was intended to compare the submitted fields with the fields that DataTran returns wasn’t working, and has been fixed. This should help eliminate the dropped character problems.6/11/01 Version 1.16.165+ dh
1. Fixed a potential bug with the feature that compares submitted fields with fields that the DataTran returns. Because the data was only memorized for regular sales, other transaction types could end up with erronious data.
2. When entering the batch screen with an error in the batch, sometimes an error 9 would result due to an out of bounds and erronious media number. This has been changed to allow the report to still run but placing the transaction into an **ERR** Media so that the report doesn’t crash.
3. When depositing a batch with bad transactions, TraPr will now strip the bad transaction into an XML file called BadTran.LOG and deposit the rest of the batch. Afterwards it will then inform the user that n bad transactions were removed. From that point on, until the BadTran.LOG is cleared out, a new Red button will appear on the batch screen that gives the user the opportunity to fix and import each bad transaction into the current batch.
4. The Batch Summary and Batch Detail report didn’t use the same calculation rules but have been modified to do so.
5. When depositing a batch, TraPr no longer prints a report first, but it does print a batch detail report afterwards, listing the exact transactions that were deposited if succesful, or the reason (if any) that it was unable to deposit. If Transactions are removed, they will not appear on this report, but the number of removed transactions will be indicated on the bottom.
6. Voids were double subtracting from the new Batch Reports. This has been fixed.6/11/01 Version 1.18.170+ dh
1. TraPr is now fully setup to handle Pre-auth sales from TouchPro. It eases the workload for TouchPro by maintaining a buffer of all the information needed to complete Pre-auth sales so that TouchPro doesn’t have to manage this information.
2. TraPr now accepts the KeyLok deviced with Prog ID 3 as an alternative to the HASP.1/19/02 Version 1.18.178+ dh
1. The KeyLok code had a bug and has been fixed. Previous versions didn’t behave correctly when the KeyLok was found.
4/20/02 Version 1.19 – 4/20/02 dh
1. There was a bug with Pre-auth that caused the Authorization code to be lost from the FIFO after a site had performed 150 Pre-auth transactions. This has been fixed.
2. There was a bug with Pre-auth that caused the DataTran to dial out when completing a prior authorized sale when it only needed to post the transaction to the batch instead. This has been fixed. -
AuthorPosts
- You must be logged in to reply to this topic.