Re: [WebDNA] Re: table comma field delimiter bug?

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108106
interpreted = N
texte = --0015175cbb0a2d7f2d04b6a0f430 Content-Type: text/plain; charset=UTF-8 Chris, I would suggest that you work to ensure that table properties match database properties. I use the merge format in a few situations - i.e. when dealing with FileMaker exports - so I would like to see this remain as an option - though I realise I may be in a minority. Take care - Tom --0015175cbb0a2d7f2d04b6a0f430 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Chris,

I would suggest that you work to ensure that tabl= e properties match database properties. =C2=A0 I use the merge format in a = few situations - i.e. when dealing with FileMaker exports - so I would like= to see this remain as an option - though I realise I may be in a minority.

Take care
- Tom
--0015175cbb0a2d7f2d04b6a0f430-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] table comma field delimiter bug? (Donovan Brooke 2012)
  2. Re: [WebDNA] table comma field delimiter bug? (Kenneth Grome 2012)
  3. Re: [WebDNA] table comma field delimiter bug? (Govinda 2012)
  4. Re: [WebDNA] table comma field delimiter bug? (Donovan Brooke 2012)
  5. Re: [WebDNA] table comma field delimiter bug? (Kenneth Grome 2012)
  6. Re: [WebDNA] table comma field delimiter bug? (Donovan Brooke 2012)
  7. Re: [WebDNA] table comma field delimiter bug? (Donovan Brooke 2012)
  8. [WebDNA] table comma field delimiter bug? (Kenneth Grome 2012)
--0015175cbb0a2d7f2d04b6a0f430 Content-Type: text/plain; charset=UTF-8 Chris, I would suggest that you work to ensure that table properties match database properties. I use the merge format in a few situations - i.e. when dealing with FileMaker exports - so I would like to see this remain as an option - though I realise I may be in a minority. Take care - Tom --0015175cbb0a2d7f2d04b6a0f430 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Chris,

I would suggest that you work to ensure that tabl= e properties match database properties. =C2=A0 I use the merge format in a = few situations - i.e. when dealing with FileMaker exports - so I would like= to see this remain as an option - though I realise I may be in a minority.

Take care
- Tom
--0015175cbb0a2d7f2d04b6a0f430-- Tom Duke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

searchable list archive (1997) Fun with Dates - revisited (1997) Deleting Orders (1998) Help Wanted - Stowe, Vermont (1999) Mail Integration (1999) Alternative colors? (2000) webmerch and serials - almost there (1997) [append] problems (2003) forming a SKU (1999) Multi-processor Mac info ... (1997) WebCat with WebTen (1998) Search for 20 finds 2000, 200 Why? (1997) ReturnRaw and redirect one last question (1997) Stopping bad HTML propagation ? (1997) no? marks in the links (2003) problems with 2 tags (1997) Sort Order on a page search (1997) WCS Newbie question (1997) creating a ShipCosts database (1997) How do I get WebCatalog to interpret WebDNA tags in.html files? (1997)