can you please fix it so you do not have to type dashes when you enter your gen ledger acct numbers...in some places you dont have to and then in others you do. ex: 600-0101-00-71
by: Kara L. | over a year ago | Financial Management
Completed
general ledger acct numbers
by: Kara L. | over a year ago | Financial Management
Comments
You should not have to type in the dashes. If you go to Account Maintenance it should pull up the number without typing the dashes.
I believe the issue is the CONSISTENTCY in typing dashes or not typing dashes. There are GL fields where you have to type the separators and others where they are assumed and filled in for you. Yes, if you are in account maintenance, you don't have to type the extra characters. But I have experienced other GL fields where you do. Just like the lack of consistency in typing dates without the slashes.
Consistency (or lack thereof) is a big irritant.
When running GL reports and you enter in your GL account with segments, the report will return "Data is not selected for report printing" due to the missing separators. Very big irritant for my clients.
Please make data entry consistent in all modules - should be able to enter a GL account number without having to key in the dashes.
The issue here is consistency. Clients shouldn't have to remember where they need to enter dashes and where they don't. Every data entry screen formats properly without entering the dashes, reporting should too.
Back in the early to middle 80s, the one of the first things that differentiated this program from competitors was the interface. Even though it was character based, the input routines automatically handled punctuation in GL accounts, Customer and Vendor accounts, SS numbers, telephone numbers, dates, etc. Dates were enhanced beyond punctuation so that 1 or 2 characters meant change the day and 3 or 4 meant change the day and month.
Other early differentiators were Lookups for everything, the ability to Preview any report, easy navigation between fields and screens and extensive use of Field defaults.
Now days, issues that can be classified NAB are not likely to change.