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:

Beta Documentation (1997) Dynamic PDFs? (2002) Triggers Suck! (2000) Calculating a total (2000) Multiple 'Users.db' files not possible (1997) X etc.... (1999) RE: what characters are replaced for tab and CR? (1998) Navigator Parsing (1997) Maybe minor bug report (1997) unsubscribe (1997) RE: template security preferences????? (1998) Attention all list readers (1997) PCS Emailer's role ? (1997) For those of you not on the WebCatalog Beta... (1997) Searching/sorting dates (1997) Shoppingcart passing price (2000) WebCat & WebTen (1997) Integration with SQL (1997) Trouble with Netscape (1998) [WebDNA] WebDNA Roll Call (2013)