> While the hethttprequestdata does indeed split them into > seperate fields, it produces another issue of sorts. There > are now two of each field however they all have the same > field name. Its not possible to differentiate which field B > goes with which field A. heh. Still an excellent thought to > test though!
If you have multiple cases of this, they should be listed in the same sequence in all cases, so you might be able to figure that out by looking at each "row". For example, let's say you have a table in your PDF which contains part ID and part name columns. In the data row of the table, you'd have, say, txtPartID and txtPartName, and in LiveCycle Designer these would be represented as arrays: txtPartID[0], txtPartName[0], txtPartID[1], txtPartName[1], etc. When the form is submitted, you should have something like this: txtPartID=5&txtPartID=23&txtPartName=widget%20one&txtPartName=widget%20two. The part name "widget one" should be associated with part ID 5 and the part name "widget two" should be associated with part ID 23. Of course, I haven't actually tested this. I'd probably just submit the data as XML and be done with it. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Training: Adobe/Google/Paperthin Certified Partners http://training.figleaf.com/ WebManiacs 2008: the ultimate conference for CF/Flex/AIR developers! http://www.webmaniacsconference.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:304577 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
