Teller creates a custom query but the journal scan only returns current business day transactions
You've configured a query within EZTeller32 or Superview32 and it returns only the current business day transactions, the default query.
Workaround:
EZTeller32 and Superview32 write the name of the custom query to a file on the PC. If users don't have full permissions on that file, only the default query will be returned.
Ask the IT tech to give all users full permission on these files
- C:\Windows\ezteller.ini
- C:\Windows\ezsuper.ini for workstation running Superview32
ArticleNumber:
000066752
Related Articles
Teller Journal is Blank after End of Day on December 31st
After balancing and declaring an End of Day on December 31st, or last working day of the year, you select View Last Transaction. When the Journal Scan screen appears, there are no transactions listed in it. Workaround: Until the system date on the ...
Unable to See Cash Count Transactions When Configuring a Custom Query in Version 5.2
Before updating to v5.2, saved custom queries opened. After updating to v5.2, you cannot see the saved cash count transactions. Environment: EZTeller Workaround: Several new transactions were added in the EZTeller release 5.2. New columns in the ...
The Starting Cash Defaults to Zero When Running Teller Cash Report for the First Business Day of the Year
In Superview32 Branch>Reports>Teller Cash Report, the starting cash will show zero for business date. Because the dated archive folders are created by calendar date, not business date, the ending cash of the last day of the previous year, December ...
Recovery From Database Disconnected When Teller Is Unable to Reconnect
EZTeller is designed so tellers can process transactions while database disconnected. If the teller stays on the same workstation using the same role, the transactions processed while database disconnected should upload once the connection to the ...
Business Day Is One Day Ahead of Correct Business Day
Your Business Day is one day ahead of the correct business day. Usually, this is caused because an End-of-Day transaction that was inadvertently performed. Workaround: You need to use the Undo End of Day menu option to reverse the End of Day ...