Shepherd's Staff 2023 Version (9.0), release 20231215
Feature
CONTRIBUTIONS
- The Contributions "Envelope box labels" report has a new option allowing you to skip labels on a sheet of labels. This option does not save with the report settings and must be set each time it is used.
Fixed
MEMBERSHIP
- If under Membership Tools/Settings, "Data entry" section, with the "require Membership Code" option checked, it was allowing users to save "Unknown/Other" as an option, instead of requiring them to pick one of the other valid codes. (Also, the screen text under the "Data entry" section of Tools/Settings has been updated for clarity.)
- If users entered two new Membership Codes in succession on the Church folder of the Person record by typing into the field and pressing TAB (rather than by using the "edit option" pop-up), the second value ended up saving with an internal number of "0", which conflicted with the first option, "Full/Professed Member".
- If under Membership Tools/Settings, "Data entry" section, with the "require Membership Code" option unchecked, if users tried to save a Member with a blank Membership Code they received the error, "Object reference not set to an instance of an object." (It now defaults to "Unknown/Other".)
- If users enter a new Membership Code on a Person record, Church tab, and choose not to add it to the list of options, they received the error, "Object reference not set to an instance of an object."
- If the user-defined field name for second church date was less than four characters (or blank), users would get the following error when printing the Church Statistics report: "Index and length must refer to a location within the string. Parameter name: length".
CONTRIBUTIONS
-
In the offering batch import for Shepherd's Staff batches, if users tried to pick a spreadsheet or other non-database file instead of "conbatch.mdb", they received the error, "Unrecognized database format...." The error message has been replaced with a user-friendly message.
FINANCE
- When importing paychecks from Payroll Mate and matching up payees to vendors in Shepherd's Staff, if the Windows user name happened to have a space in it, users received a "syntax error in FROM" clause message.
- When printing checks, if users accidentally entered a decimal point in the starting number (e.g., "1.234" or "1234."), they received the error, "Input string was not in the correct format."
- When printing checks, it allowed users to enter a negative number as the starting check number.
- When printing checks, if users entered an excessively large number for the starting check number (such as all 9's), they received the error, "Value was too large or too small for an Int32." The error has been replaced with a user-friendly message. (Note: The highest number allowed is 2,147,483,647.)
- If users tried to open the Budget window for an account with an open parenthesis in the account name (e.g., "My Account (1)"), they received the following error: "Input string was not in the correct format."
- In the dedicated account Budget window, if users had an account with an open parenthesis in the account name (e.g., "My Account (1)"), they received the following error when clicking the up and down scroll buttons to switch to that account: "Input string was not in the correct format."
- In the income/expense account Budget window, if users had an account with an open parenthesis in the account name (e.g., "My Account (1)"), they received the following error when clicking the up and down scroll buttons to switch to that account: "Input string was not in the correct format."
Change
CONTRIBUTIONS
- The offering batch import for Shepherd's Staff batches no longer has an "All files (.)" filter option when you select a file to import, since files other than the specified "conbatch.mdb" Access database file are not supported.