Re: [WebDNA] Re: table comma field delimiter bug?
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108099
interpreted = N
texte = --0015175cab784802f304b663e6bb Content-Type: text/plain; charset=UTF-8 Ken, Hi - I have experienced the same issues as yourself. The discussion at the time clarified that commas were interpreted as field delimiters within tables and could not be used. The simplest way to deal with this is to set up your table but then add data using [append] and [url]'ing the values. - Tom --0015175cab784802f304b663e6bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ken,
Hi - I have experienced the same issues as yourself= . =C2=A0 The discussion at the time clarified that commas were interpreted = as field delimiters within tables and could not be used.
The simplest way to deal with this is to set up y= our table but then add data using [append] and [url]'ing the values.
- Tom
--0015175cab784802f304b663e6bb--
Associated Messages, from the most recent to the oldest:
--0015175cab784802f304b663e6bb Content-Type: text/plain; charset=UTF-8 Ken, Hi - I have experienced the same issues as yourself. The discussion at the time clarified that commas were interpreted as field delimiters within tables and could not be used. The simplest way to deal with this is to set up your table but then add data using
[append] and
[url]'ing the values. - Tom --0015175cab784802f304b663e6bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ken,
Hi - I have experienced the same issues as yourself= . =C2=A0 The discussion at the time clarified that commas were interpreted = as field delimiters within tables and could not be used.