all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Notes:
|
|
Questions & Ideas for Multiple Decimal Places: 1. Currently (as of 7/9/09) all numbers that allow decimal places are forced to two decimals. We have a need for companies to be able to track factions of items and also fraction of pennies per item (both cost and price related). We also have a need to track weights and fractional weights extended to multi decimal points. 2. A couple of known issues: a. Database Storage: - Currently all decimals are set to (9, 2) where nine is the max digits and two is the decimal places. (9,999,999.99 – 9 total digits, 2 decimal places) - I don’t want to expand all tables and fields. The default is two decimal places and should work for 95% of our users. - I’m thinking that a separate table might be in order. I would like to keep everything else as small as possible especially since this (multi decimals) is not the default. b. Output and formatting: - Currently al output is formatted to two decimal places. What would it look like with some formatted to 2,3,4,5,6… places. I would think that it would look funny or inconsistent. - How would I control the formatting? One of the problems would be lining up the decimal point for adding. - It might require a dynamic mask value to be generated and then assigned during page output. - If I have to do different math, it might slow the pages down. This could include page queries and drill-down options. - How do I control permissions and options? - What about rounding error? c. Where do these values (multi and extended multi) need to show up? - When entering parts on a PO - When adding or editing a part number in the database - When using parts in the shopping cart - Quotes - Invoices - Printable invoices - Pdf’s - Profit per line - Recipes d. How do these changes effect the financials? - I.S. i. Revenue ii. COGS - B.S. i. Inventory counts & values ii. Payables & amounts iii. Indirectly – net profit 3. Possible ways to control the use of multi decimals: a. Corp-wide settings b. User maintained (open) allow user to set detail level – default to 2 c. Dynamic (limited open) watch from the background 4. On weight output, I think a var char (25) field would be best. That way the user could put the value in lbs., oz., grams, or mixed. It could be left blank, straight numeric, or any alpha-numeric combo. Multi decimal samples: (Please see scan in photo gallery) |