1. 'The' eliminator. A sort field which is invisible to any viewer and which consists of the company name with any leading 'The' removed and a trailing '<space>(The)' created. ex: field='company'='The Gap' and field='co-sort'='Gap (The)'. In any list view, record would appear alphabetically with the G's. The sort field entry, once it has been created, must be editable by the Administrator with discretionary override privileges.
2. Date and time auto-enter
4. Modify Record actually creates a new record and hides the old record.
5. Format numbers as money. User enters '515' and record shows '$5.15'.
alt
If there are 2 entry fields 'Dollars' and 'Cents' requiring 2 numeric entries, '5' and '15', program enters '5.15' into the database.
6. Required fields. If no entry or 'space', SUBMIT is rejected with an explanation.
7. Conditionally required fields. As above, however conditionally applied: If 'Country' = 'USA' or 'Canada' the field 'zip_postal_code' is required, else not required.
8. Alphanumeric Unique ID creator. An automatically created text field from a numeric ID field: '1' becomes '000001', '202' becomes '000202', etc.
9. Wrong format detector. If 'Name' is all upper case (JOE SMITH) or all lower case (joe smith) or a wierd mix (JOe smIth), SUBMIT is rejected with an explanation.
We're trying to evaluate DBMan's suitablity for our use, and we're NOT programmers. I expect that for each case the possible response would be one of these:
A. DBMan does this now.
B. A mod already exists to accomplish this
C. You're thinking about this wrong, there's a better way to approach it.
D. This requires some (a little or a lot) of programming, but it can be done.
E. Forget it.
Thanks,
Paul Brown
2. Date and time auto-enter
4. Modify Record actually creates a new record and hides the old record.
5. Format numbers as money. User enters '515' and record shows '$5.15'.
alt
If there are 2 entry fields 'Dollars' and 'Cents' requiring 2 numeric entries, '5' and '15', program enters '5.15' into the database.
6. Required fields. If no entry or 'space', SUBMIT is rejected with an explanation.
7. Conditionally required fields. As above, however conditionally applied: If 'Country' = 'USA' or 'Canada' the field 'zip_postal_code' is required, else not required.
8. Alphanumeric Unique ID creator. An automatically created text field from a numeric ID field: '1' becomes '000001', '202' becomes '000202', etc.
9. Wrong format detector. If 'Name' is all upper case (JOE SMITH) or all lower case (joe smith) or a wierd mix (JOe smIth), SUBMIT is rejected with an explanation.
We're trying to evaluate DBMan's suitablity for our use, and we're NOT programmers. I expect that for each case the possible response would be one of these:
A. DBMan does this now.
B. A mod already exists to accomplish this
C. You're thinking about this wrong, there's a better way to approach it.
D. This requires some (a little or a lot) of programming, but it can be done.
E. Forget it.
Thanks,
Paul Brown