> > Try TEXT TO artfield TEXTMERGE NOSHOW PRETEXT 2
> > The PRETEXT value was added to trim out the leading spaces or
> > tabs(2=tabs) which will make the string look good in code(properly
> > indented), but be compact when you send it to the server.
> And thus will be better because it's not as many bits traveling across
> the network to the server....right?
That's the general idea. There's other parameters that will take out
carriage returns as well in case the SQL server doesn't support them
or something... Or possibly creating a VFP SQL string for macro
substitution...
It's also important in a couple of my indent-aware intellisense
scripts, such as this one:
LPARAMETER oFoxCode
oFoxCode.ValueType = "V"
LOCAL lcText, lcIndent
lcIndent = LEFT(oFoxCode.FullLine, ATC(ALLTRIM(oFoxCode.Abbrev),
oFoxCode.FullLine)-1)
TEXT TO lcText NOSHOW TEXTMERGE PRETEXT 2
LOCAL liOldArea
<<lcIndent>>liOldArea = SELECT(0)
<<lcIndent>>~
<<lcIndent>>SELECT (liOldArea)
ENDTEXT
RETURN lcText
--
Derek
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
