I don't think the formatting bit is the problem. Execute in 4D is subject to all of the restrictions of 4D's EXECUTE command. You say "the same $vt_Content works fine in a 4D method". Does that mean you tried the code on its own, or did you try running it through the execute command?
On 2/20/06, Steve Alex <[EMAIL PROTECTED]> wrote: > > Is the %s formatting operator limited to string(255) when used in > conjunction with "execute in 4d"? > > Though I found a way to use the new stuff in v4 to avoid plugin > wrappers. > > Following snippet causes PDF Plugin to barf with "End character '>' > for inline option list not found" > > $cmd := 'PDF Create Text Flow(%d;"%s")' % ($vl_PDFRef;$vt_Content) > $vl_TextFlow:= execute in 4d($cmd;*) > > $vt_Content is about a 2000 character text field (typed). It is an > inline text file to be processed by PDF Plugin. Dumping locals shows > $cmd correctly formated. > Since it uses <> as parsing characters, I can only assume that it is > being truncated because the same $vt_Content works fine in a 4D method. > > Steve Alex > AIDT > > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev > Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ > _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
