Field question

[Stephen Barncard]

In rev, there are many ways to do similar tasks.

>
>BUT, if any of these fields contain a large amount of text where there is a
>possibility that it may include a comma, tab or return character then your
>output may not be as expected, ie if you use the return character as



And why I mentioned  URLencoding each block of data as it forces all 
text to a single line. (Base64 will do this too if you include a way 
to deal with returns).
This is very speedy and useful, for


storing complex dialog prompts in htmltext, so they can be put into a 
variable that displays on one line:

local htmlselectToexportHtml = 
"%3Cp%3E%3Cfont+size%3D%2219%22+color%3D%22%234F483A%22%3E%3Cb%3ESelect+Fields+To%3C%2Fb%3E%3C%2Ffont%3E%3C%2Fp%3E%0D%0A%3Cp%3E%3Cfont+size%3D%2223%22+color%3D%22%239D1B1B%22%3E%3Cb%3EEXPORT%3C%2Fb%3E%3C%2Ffont%3E%3C%2Fp%3E"
put urldecode(htmlselectToexportHtml) into pPrompt

or storing data inside of data in a 'flat' array'

key1  <tab> 
U0VMRUNUICogIEZST00gYERldmljZXNfTWFpbmAgT1JERVIgQlkgYDxvcmRlckJ5PmAgPGRpcj4= 
	(Base64Encode)
key2  <tab> SHOW+DATABASES%3B%0D%0A       (URLEncode)
key3  <tab> this is textwith returns in itto showreplaced by 
vertical tabs.     (returns converted to vertical tabs)

the vertical tabs (ASCII 11 dec) character is what Filemaker uses to 
deal with returns in fields on export. It's almost a standard.


sqb
-- 


stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -