How to add trailing asterisks after Check Amount in words?

[GPLoveHateRelationship]

Is it possible to add trailing astersiks (*) symbols after the check dollar
amount in words?

For example, suppose I have a check for $150, I'd like the check amount in
words to read "One Hundred Fifty Dollars*************"

The purpose of adding these trailing asterisks is obviouslly to prevent
anyone from modifying the check for a larger amount.

Please let me know if the asterisks can be added to check in Report Writer.
Also, please keep in mind the trailing asterisks would have to be dynamic,
not static, in the sense that the amount of asterisks should be able to
change relative to the length of dollar amount in words.

Please help. Any input greatly appreciated. Thanks!

[Mariano Gomez]

GPLHR,

Since the Check Stubs use String A 255 and String B 255 from the
PM_Payment_Work directly, you will need to create 2 conditional calculated
fields, as follow:

(C) String A 255
Returns: String
Condition: PM_Payment_Work.String B 255 <> ""
True Case: PM_Payment_Work.String A 255
False Case: FUNCTION_SCRIPT(RW_PadWithStars PM_Payment_Work.String A 255)

(C) String B 255
Returns: String
Condition: PM_Payment_Work.String B 255 <> ""
True Case: FUNCTION_SCRIPT(RW_PadWithStars PM_Payment_Work.String B 255)
False Case: PM_Payment_Work.String B 255

The RW_PadWithStars user-defined function can be found under the Financial
series.

Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com

[GPLoveHateRelationship]

Hi Mariano,

Thanks for your feedback to my question.

I tried those RW_PadWithStars function in calc fields as you described, but
I get an error when generating the report: "Error in Equation: Illegal Syntax"

Any ideas why I'm getting this? Does it work for you?

[Mariano Gomez]

My bad! Don't have my head straight lately.

(C) String A 255
Returns: String
Condition: PM_Payment_Work.String B 255 <> ""
True Case: PM_Payment_Work.String A 255

False Case: FUNCTION_SCRIPT(RW_PadWithStars PM_Payment_Work.String A 255, 255)

(C) String B 255
Returns: String
Condition: PM_Payment_Work.String B 255 <> ""

True Case: FUNCTION_SCRIPT(RW_PadWithStars PM_Payment_Work.String B 255, 255)

False Case: PM_Payment_Work.String B 255

NOTE: I introduced the comma between the Function_Script parameters ONLY for
readability sake. Do not use any commas.

[Mariano Gomez]

Check my new blog article at
http://dynamicsgpblogster.blogspot.com/2008/11/how-to-add-trailing-asterisks-after.html

[GPLoveHateRelationship]

Hi Mariano,

Thanks for the updated formulas for the Calculated Fields used to add
trailing asterisks after check amount it words.

I tried what you suggested and it worked!!! Thank you very much.

However, I did find one big limitation. The calculated fields do not work
(truncate) check amount in words if the check amount is very large and it
does not show the trailing asterisks.

For example, say we have a check for $987,654.32, a fairly large amount.
With the calculated fields you suggested to create, the check only displays
"Nine Hundered Eighty Seven Thousand Six Hundered Fifty Four". It does not
finish with "32 cents" nor does it add the trailing asterisks ***, and nor
does it spill onto the next field String B 255.

But if I remove security on the modified report and reprint the same check
it prints correctly "Nine Hundered Eighty Seven Thousand Six Hundered Fifty
Four and 32 cents"

So while your calculated field expressions does add trailing asterisks after
check amount in words, it does not seem to work for large dollar value check
amounts. Please feel free to give it a try and let me know if you have any
suggestions...thanks so very much!

[Mariano Gomez]

GPLHR,

I will look into this. The problem may be with the second calculated field -
(C) String B 255.

[Mariano Gomez]

OK,

I did a test on this and found that the amount is actually in the STR 255 A
string. The STR 255 B string column is blank in the PM10300. This leads me to
believe that your string field is shorter on the modified report than it
originally was before you modify it. You should perhaps try to increase the
size of the field on the modified report.

Other things you may want to look at if you are using graphical reports is
the font and font size, when compared to the original report.

Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com

[GPLoveHateRelationship]

Hi MGomez,

Thanks for your in-depth research on this matter.

Actually the string field size of STR 255 A and B on my modified report is
not shorter than the original (unmodified) report. I kept everything the same
length and I even tried increasing the size of the field but that does not
work either.

I am using a "Check with Stub on Bottom" which is a Text Report by default
(not graphical) so font and font size should not be an issue.

Something else funky is going on, because I am literally using same formats
as the original unmodified Check with Stub on Bottom. The only thing I did
was create those calculated fields as you suggested and replaced them with
STR 255 A and STR 255 B.

I will research it further on my side and if you happen to find what is
causing it please let me know. Thanks again very much for helping
out...appreciate it v much

[Mariano Gomez]

I found the problem. Report Writer string calculated fields are truncated to
80 characters. You can read this up on my blog at
http://dynamicsgpblogster.blogspot.com/2008/11/length-of-report-writer-calculated.html.
If you assing any length string over 80 chars, it will be truncted at 80
chars.

Now with the example in question, $987,654.32, I was able to get it to print
untruncated and with one asterisk using the Stub on Top and Bottom - Text,
but did not try with any other stub format.