Quote:Scott, I tried to resist, but I just can't...
I must know: why do you need to do this?
I don't actually
need to do it, I'm considering it as a convenience for my Accounts Payable person.
Here's the situation: whenever we institute a wire transfer through our bank, we are required to present to them a unique "key" number that is derived in a rather oblique way. We have a "private number" that has been issued to our company, plus a sheet of codes. Each month has a unique number code, as does each day of the month. Then the amount we are transferring has a code which is determined as such: the millions amount has a code, as does the hundred thousands, as does the ten thousands, and so on. Once we determine all the individual codes we have to add them up, and the total is the "key code" for the transaction. So, for example:
For a transfer made January 1 in the amount of $128,750.00:
Value Code
Our number: 1234
January: 345
1st: 7668
100,000: 568
20,000: 3577
8,000: 980
700: 3664
50: 296
0: 0
Total (Key Code): 1234 + 345 + 7668 + 568 + 3577 + 980 + 3664 + 296 + 0 = 18332
I had no idea until yesterday she was going through this much BS, so I immediately created a Sesame form that would do the work for her, hard-coding all the key values in so all she has to do is pick a month, a day, a Millions value, a Hundred Thousands value, etc. It's working well and will save a lot of time and hassle. Then I thought, if the work required in coding wasn't too much trouble, an element where she could just put in the value to be transferred would be nice, and let Sesame break the sucker down. I'm still undecided. What I've got is working well and it only took about 15 minutes of work.
I may come back to the "dissect a number" idea if I've got some free time, but my boss plunked three new projects onto me this morning so it will have to wait. Thanks to Bob and Ray for the advice.