Re: Fwd: [WebDNA] Fails to recognize comma-separated db

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105395
interpreted = N
texte = --001485f859744b8c670489c249bc Content-Type: text/plain; charset=ISO-8859-1 Ken, if you read the documentation, it does not say that it supports CVS files or any comma delimited file, it specifically says that it supports the Filemaker Pro quote-comma delimited format. Basically, the functionality was added specifically for the users of Filemaker Pro so they could export their databases and be used that way by WebDNA. This was at a time when Filemaker Pro was widely used in the Mac environment. Sal On Wed, Jun 23, 2010 at 8:24 PM, Kenneth Grome wrote: > I don't know why webdna was ever coded to require two different formats for > field names and field values in csv files, but it seems like a foolish way > to do it -- because it is NOT consistent with tab-delimited format which > uses tabs to separate both field names *and* field values. > > What I got from my online bank was a file that had both the field values > and the field names separated by commas. It failed in webdna. Then I > modified the file by surrounding all the commas with quotes to make it a > "quote-comma-quote" separated file. This also failed in webdna. > > According to your example we must use ONLY commas to separate field names, > then we have to use commas surrounded by quotes to separate field values. > In other words, we have to use two different formats if we expect webdna to > work properly with csv files. > > Why are we required to use two different formats in the same file in order > for webdna to use that file successfully as one of its databases??? > > Personally I think it would "make sense" to re-code webdna so that it can > handle csv files that use ONLY commas as separators for both field names and > field values, and so that it cal also handle csv files that use commas > surrounded by quotes as separators for both field names and field values -- > since these are the typical ways csv files are formatted in the industry (in > my experience anyways). > > By the way, I'm assuming that the different format requirement for field > names vs. field values is the cause of my problem. Is this the actual cause > ... or is something else going on here? > > Sincerely, > Kenneth Grome > > > > > > > > > Hello everybody, and particularely Ken, Matt and Stuart. We would not > like to leave a bug if there is a problem with the Merge format. Please, > could you confirm there is indeed a problem of databases not read using this > format? in this case, woud you be so kind to post the field names format and > one or two lines of your databases. > > > > As explained in WebDNA website, the proper format is > > > > ---------------------------------------------------------------- > > name,address,city,state,zip > > "Grant","1180 Central Ave","San Marcos","CA","92079" > > "PCS","11770 Bernardo Plaza Court","San Diego","CA","92128" > > ---------------------------------------------------------------- > > > > and it works, at least for me. Here a small test: just upload this to any > WebDNA served website and open "states2.dna" file with your browser. > > > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 > --001485f859744b8c670489c249bc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ken, if you read the documentation, it does not say that it supports CVS fi= les or any comma delimited file, it specifically says that it supports the = Filemaker Pro quote-comma delimited format.=A0 Basically, the functionality= was added specifically for the users of Filemaker Pro so they could export= their databases and be used that way by WebDNA.=A0 This was at a time when= Filemaker Pro was widely used in the Mac environment.



Sal

On Wed, Jun 23, 2010 at 8= :24 PM, Kenneth Grome <kengrome@gmail.com> wrote:
I don't know why webdna was ever coded to require two different formats= for field names and field values in csv files, but it seems like a foolish= way to do it -- because it is NOT consistent with tab-delimited format whi= ch uses tabs to separate both field names *and* field values.

What I got from my online bank was a file that had both the field values an= d the field names separated by commas. =A0It failed in webdna. =A0Then I mo= dified the file by surrounding all the commas with quotes to make it a &quo= t;quote-comma-quote" separated file. =A0This also failed in webdna.
According to your example we must use ONLY commas to separate field names, = then we have to use commas surrounded by quotes to separate field values. = =A0In other words, we have to use two different formats if we expect webdna= to work properly with csv files.

Why are we required to use two different formats in the same file in order = for webdna to use that file successfully as one of its databases???

Personally I think it would "make sense" to re-code webdna so tha= t it can handle csv files that use ONLY commas as separators for both field= names and field values, and so that it cal also handle csv files that use = commas surrounded by quotes as separators for both field names and field va= lues -- since these are the typical ways csv files are formatted in the ind= ustry (in my experience anyways).

By the way, I'm assuming that the different format requirement for fiel= d names vs. field values is the cause of my problem. =A0Is this the actual = cause ... or is something else going on here?

Sincerely,
Kenneth Grome







> Hello everybody, and particularely Ken, Matt and Stuart. We would not = like to leave a bug if there is a problem with the Merge format. Please, co= uld you confirm there is indeed a problem of databases not read using this = format? in this case, woud you be so kind to post the field names format an= d one or two lines of your databases.
>
> As explained in WebDNA website, the proper format is
>
> ----------------------------------------------------------------
> name,address,city,state,zip
> "Grant","1180 Central Ave","San Marcos",= "CA","92079"
> "PCS","11770 Bernardo Plaza Court","San Diego= ","CA","92128"
> ----------------------------------------------------------------
>
> and it works, at least for me. Here a small test: just upload this to = any WebDNA served website and open "states2.dna" file with your b= rowser.
>
>
-----------------------------= ----------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
old archives: http://dev.webdna.us/TalkListArchive/
Bug Reporting: http://forum.webdna.us/eucabb.html?pa= ge=3Dtopics&category=3D288

--001485f859744b8c670489c249bc-- Associated Messages, from the most recent to the oldest:

    
  1. Re: Fwd: [WebDNA] Fails to recognize comma-separated db ("Psi Prime Inc, Matthew A Perosi " 2010)
  2. Re: Fwd: [WebDNA] Fails to recognize comma-separated db (sal danna 2010)
  3. Re: Fwd: [WebDNA] Fails to recognize comma-separated db (Kenneth Grome 2010)
  4. Fwd: [WebDNA] Fails to recognize comma-separated db (christophe.billiottet@webdna.us 2010)
--001485f859744b8c670489c249bc Content-Type: text/plain; charset=ISO-8859-1 Ken, if you read the documentation, it does not say that it supports CVS files or any comma delimited file, it specifically says that it supports the Filemaker Pro quote-comma delimited format. Basically, the functionality was added specifically for the users of Filemaker Pro so they could export their databases and be used that way by WebDNA. This was at a time when Filemaker Pro was widely used in the Mac environment. Sal On Wed, Jun 23, 2010 at 8:24 PM, Kenneth Grome wrote: > I don't know why webdna was ever coded to require two different formats for > field names and field values in csv files, but it seems like a foolish way > to do it -- because it is NOT consistent with tab-delimited format which > uses tabs to separate both field names *and* field values. > > What I got from my online bank was a file that had both the field values > and the field names separated by commas. It failed in webdna. Then I > modified the file by surrounding all the commas with quotes to make it a > "quote-comma-quote" separated file. This also failed in webdna. > > According to your example we must use ONLY commas to separate field names, > then we have to use commas surrounded by quotes to separate field values. > In other words, we have to use two different formats if we expect webdna to > work properly with csv files. > > Why are we required to use two different formats in the same file in order > for webdna to use that file successfully as one of its databases??? > > Personally I think it would "make sense" to re-code webdna so that it can > handle csv files that use ONLY commas as separators for both field names and > field values, and so that it cal also handle csv files that use commas > surrounded by quotes as separators for both field names and field values -- > since these are the typical ways csv files are formatted in the industry (in > my experience anyways). > > By the way, I'm assuming that the different format requirement for field > names vs. field values is the cause of my problem. Is this the actual cause > ... or is something else going on here? > > Sincerely, > Kenneth Grome > > > > > > > > > Hello everybody, and particularely Ken, Matt and Stuart. We would not > like to leave a bug if there is a problem with the Merge format. Please, > could you confirm there is indeed a problem of databases not read using this > format? in this case, woud you be so kind to post the field names format and > one or two lines of your databases. > > > > As explained in WebDNA website, the proper format is > > > > ---------------------------------------------------------------- > > name,address,city,state,zip > > "Grant","1180 Central Ave","San Marcos","CA","92079" > > "PCS","11770 Bernardo Plaza Court","San Diego","CA","92128" > > ---------------------------------------------------------------- > > > > and it works, at least for me. Here a small test: just upload this to any > WebDNA served website and open "states2.dna" file with your browser. > > > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 > --001485f859744b8c670489c249bc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ken, if you read the documentation, it does not say that it supports CVS fi= les or any comma delimited file, it specifically says that it supports the = Filemaker Pro quote-comma delimited format.=A0 Basically, the functionality= was added specifically for the users of Filemaker Pro so they could export= their databases and be used that way by WebDNA.=A0 This was at a time when= Filemaker Pro was widely used in the Mac environment.



Sal

On Wed, Jun 23, 2010 at 8= :24 PM, Kenneth Grome <kengrome@gmail.com> wrote:
I don't know why webdna was ever coded to require two different formats= for field names and field values in csv files, but it seems like a foolish= way to do it -- because it is NOT consistent with tab-delimited format whi= ch uses tabs to separate both field names *and* field values.

What I got from my online bank was a file that had both the field values an= d the field names separated by commas. =A0It failed in webdna. =A0Then I mo= dified the file by surrounding all the commas with quotes to make it a &quo= t;quote-comma-quote" separated file. =A0This also failed in webdna.
According to your example we must use ONLY commas to separate field names, = then we have to use commas surrounded by quotes to separate field values. = =A0In other words, we have to use two different formats if we expect webdna= to work properly with csv files.

Why are we required to use two different formats in the same file in order = for webdna to use that file successfully as one of its databases???

Personally I think it would "make sense" to re-code webdna so tha= t it can handle csv files that use ONLY commas as separators for both field= names and field values, and so that it cal also handle csv files that use = commas surrounded by quotes as separators for both field names and field va= lues -- since these are the typical ways csv files are formatted in the ind= ustry (in my experience anyways).

By the way, I'm assuming that the different format requirement for fiel= d names vs. field values is the cause of my problem. =A0Is this the actual = cause ... or is something else going on here?

Sincerely,
Kenneth Grome







> Hello everybody, and particularely Ken, Matt and Stuart. We would not = like to leave a bug if there is a problem with the Merge format. Please, co= uld you confirm there is indeed a problem of databases not read using this = format? in this case, woud you be so kind to post the field names format an= d one or two lines of your databases.
>
> As explained in WebDNA website, the proper format is
>
> ----------------------------------------------------------------
> name,address,city,state,zip
> "Grant","1180 Central Ave","San Marcos",= "CA","92079"
> "PCS","11770 Bernardo Plaza Court","San Diego= ","CA","92128"
> ----------------------------------------------------------------
>
> and it works, at least for me. Here a small test: just upload this to = any WebDNA served website and open "states2.dna" file with your b= rowser.
>
>
-----------------------------= ----------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
old archives: http://dev.webdna.us/TalkListArchive/
Bug Reporting: http://forum.webdna.us/eucabb.html?pa= ge=3Dtopics&category=3D288

--001485f859744b8c670489c249bc-- sal danna

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:

Re1000001: Setting up shop (1997) Electronic Delivery (1997) Spell Check (2003) Smart caching problems with 2.1b3? (1997) Showif, Hideif reverse logic ? (1997) Hideif on IP range (2004) Reversed words (1997) need help with [sendmail] and [showif]s (1998) File not found error message (1998) URGENT - CPU usage OSXS (2001) Re:quit command on NT (1997) WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997) Three new problems, maybe a fourth (1997) Error 404 problem (2003) recommendations for credit card software (1998) PSC recommends what date format yr 2000??? (1997) [searh] or [shownext]problem (1998) Replace Missing Images (2003) WebCat2: Items xx to xx shown, etc. (1997) [WriteFile] problems (1997)