Frothingslosh
Premier Pale Stale Ale
- Local time
- Today, 08:07
- Joined
- Oct 17, 2012
- Messages
- 3,276
I'm trying to build what is supposed to be a very simple invoicing app, and running into nothing but problem after problem after problem.
In a nutshell, accounting exports invoicing data into a spreadsheet, and I'm to import this spreadsheet into the invoicing tool and generate the invoice.
Sounds easy enough, but there's a hitch: due to inconsistant entry, for a number of records, numeric fields have been left blank. Most of them are null entries, which is fine, I have a function that converts those to $0 values for billing purposes. What's killing me is that SOME of the fields are linking as #Num! rather than a value or a null, and I can't seem to do anything with those. :banghead:
I've tried converting any value to 0 that returns FALSE value from IsNumeric; I've even tried formulas that return a 0 if the looked up value is an error, but that bloody error propagates through everything I've attempted.
So, does anyone have any suggestions? After this, I get to move on to trying to limiting record adding to unique rows when the 'unique identifier' is 11 fields long because of management requirements.
In a nutshell, accounting exports invoicing data into a spreadsheet, and I'm to import this spreadsheet into the invoicing tool and generate the invoice.
Sounds easy enough, but there's a hitch: due to inconsistant entry, for a number of records, numeric fields have been left blank. Most of them are null entries, which is fine, I have a function that converts those to $0 values for billing purposes. What's killing me is that SOME of the fields are linking as #Num! rather than a value or a null, and I can't seem to do anything with those. :banghead:
I've tried converting any value to 0 that returns FALSE value from IsNumeric; I've even tried formulas that return a 0 if the looked up value is an error, but that bloody error propagates through everything I've attempted.
So, does anyone have any suggestions? After this, I get to move on to trying to limiting record adding to unique rows when the 'unique identifier' is 11 fields long because of management requirements.