I've been trying to implement the new WordMerge programming found in the Feb. 08 edition of InsideSesame and everything is working pretty well, except that a large multi-line text field isn't being listed as a field that can be merged. From the InsideSesame article:
Quote:As already noted, the other big improvement is that
WordMerge now automatically generates the list of
mergeable LE names. The external text file has been
eliminated by a subroutine that makes a list of all the
elements on the form, then weeds out the ones that can’t
contain editable data, such as static text and command
buttons. Here’s the new subroutine in full:
SUBROUTINE MergeFields()
// Make a list of the LE’s that can contain editable data
var n as Int
var nn as Int
For n = 1 to @CountStringArray(vLEs)
vName = @AccessStringArray(vLEs, n)
SetThisElement(vName)
nn = @ElementType(ThisElement)
// If in following range, LE supports editable data
If nn > 999 and nn < 1009
// Add to the list of LEs exported for mailmerge
vNames = @AppendStringArray(vNames, vName)
UnSetThisElement()
Next
The steps I took were:
1. Ran a command button containing "var vLEs as String = @StringArrayElementList()"
and found that the name of the field did in fact show up.
2. Then I checked to see the @ElementType for the field and it returned '1024' -- which would invalidate it as an editable field according to the programming. The programming manual doesn't list what a LE with a type of '1024' would be.
Also, the WordMerge programming removes @NewLine(), but my text field makes use of the command -- is there any way around that? What I have is a form for generating estimates for custom products. The field in question is called 'EstimateText' -- and hence can have several @NewLine() calls. Any suggestions?
Pages: 1
Send Topic 
Print
WordMerge for 2.05 -- trouble with text field (Read 553 times)
