4Site
Support Request System
View Patch #40.034.020
Description
Patch ID:
Date Implemented:
Patch Title:
Patch Type:
Request IDs:
Bug
Enhancement
Other
01823 -
Voucher query processes Refresh differently from Enter after vo# entry
Symptoms:
I had vouchers in a zzzzz SYSTEM format eg. 99997 and 99998.USER format is ssssssss. Then I expanded the vo SYSTEM format to zzzzzzzzzz and entered 0000099999. The voucher app could find both old and new vouchers - old ones passed the USER format now. The VO Query app sometimes found them. If I typed in 99997 and hit Refresh it did not find them - it actually changed my number to 0000099997 and seemed to just check the SYSTEM format. However, if I typed in 99997 and hit Enter it did find it. So it's inconsistent in it's formatting of the numbers.
Solution:
To process pre-existing vouchers with the zzzzz format, pre-test the entered VoId, and if it exists on the vohdr table, pass it as the void parameter to the refresh selection query sql. Otherwise, format the VoId entry to the zzzzzzzzzz format (using clsKey.KeyFormat) and pass the returned 0-padded value as the VoId parameter.
Browse Patches
Find a Patch
Return to Request System Menu
