When I print numbers or currency with wordmerge, the numbers come out with 6 decimal places.  In Sesame the numbers are formatted with 0 deciimal places, but when the numbers are in the customer.txt file, they already have the extra decimal places, so it doesn't seem like it's a MS Word issue. Has anyone else found this or know how to correct it?

Bharat,

Thanks for the direction.  Could I trouble you for some more details, because I can't seem to get the converted text to calculate.  I have three text elements, QTY, PRICE, EXT PRICE What I need is for the QTY * PRICE = EXT PRICE, and for each money element  to have two decimal places, and the QTY to have no decimal places, when it gets printed (or viewed in TableView).  (Do you know of any plans to correct this in future releases, so we don't have to build the work around?)
Thanks for your help.

If you need to wordmerge all namely,

Price
Quantity
Extended_Price

Format all of them as Text

following code goes in Price, element exit event

Price = "$" + @decimals (Price, 2)

Following code goes in Extended_Price element exit event

var vPrice as Double
var vQuantity as int

vPrice = @right (Price, (@len (Price) - 1))
vQuantity = @tonumber (Quantity)


Extended_Price = @str (vPrice * vQuantity)
Extended_price = "$" + @decimals (Extended_Price, 2)

Let me know how does this work.

Quote:


PeterG, I see why you want to have this to have permanent solution. For all caclulation involved, you have to keep on using typecast functions.

The way the value of number fields and Money Fields are stored is the Foundation blocks of Sesame. So do not expect to have any changes there.

In the wordmerge utility, value of Array elements can be changed when they are number or money format (with multiple 000000) also the date format nn/nn/nnnn can be manupulated at the array level before they are merged.

   
I believe a few lines of code in Wordmerge utility will do it (as I see the same correction codes have been included in the "Merge Printing Database Records Internally" in appendix 2).  However, I believe it should be done by the Sesame Development Team and included in the Wordmerge utility becasue this particular utility has become the essential part of Sesame for many for their printing needs. I hope, lanticans have been listening.