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

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105396
interpreted = N
texte = This is a multi-part message in MIME format. --------------080801080601070308030006 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I do see my confusion with all of this now too. Although the docs do say "Filemaker" I'm not a filemaker user and therefore would not know there as a difference. Also, I've never used the .db format with the first row as the field names. All my previous attempts were with the .hdr file. So I should assume that the CSV format only works when self contained within the .db file only. As for the issues Stuart mentioned with numerical and text fields that include commas... I've had the same exact issues and also developed my own cleaning methods. I don't have the time right now to test this on my own, but I will watch this thread with curiosity. I have a large project coming up in August that will need the CSV import format and I'll be ecstatic if this works. I'll report back at a later time with my particular findings. Thanks for covering this topic again.... too bad no one mentioned the details below 5 years ago. Matt christophe.billiottet@webdna.us wrote: > 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. > > > ------------------------------------------------------------------------ > > > > - chris > > > > > Begin forwarded message: > > >> From: christophe.billiottet@webdna.us >> Date: June 22, 2010 22:40:02 GMT-03:00 >> To: >> Subject: Re: [WebDNA] Fails to recognize comma-separated db >> Reply-To: >> >> Sorry, i cannot reproduce: do you follow the format explained at http://www.webdna.us/database-format.dna? >> >> for instance >> >> ---------------------------------------------------------------- >> name,address,city,state,zip >> "Grant","1180 Central Ave","San Marcos","CA","92079" >> "PCS","11770 Bernardo Plaza Court","San Diego","CA","92128" >> ---------------------------------------------------------------- >> >> >> >> Here a small example: >> >> >> - chris >> ============================ >> WebDNA Software Corporation >> 16192 Coastal Highway >> Lewes, DE 19958 >> >> On Jun 22, 2010, at 22:06, Stuart Tremain wrote: >> >> >>> Me too ...... >>> >>> >>> Regards >>> >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>> >>> >>> >>> >>> On 23/06/2010, at 10:30 AM, christophe.billiottet@webdna.us wrote: >>> >>> >>>> Anyone with the same problem Ken found? >>>> >>>> - chris >>>> ============================ >>>> WebDNA Software Corporation >>>> 16192 Coastal Highway >>>> Lewes, DE 19958 >>>> >>>> On Jun 22, 2010, at 21:24, Kenneth Grome wrote: >>>> >>>> >>>>>> Well, i have no idea: it is the first time i hear someone speaking about such a problem. As far as i know, WebDNA started to read comma-separated databases in 1997, this specific code has not been changed since then. >>>>>> >>>>> Since it no longer works the way it did in 1997, maybe now is a good time to remove the part of webdna's description that says it can open and read comma-delimited db's without modification. >>>>> >>>>> Sincerely, >>>>> Kenneth Grome >>>>> --------------------------------------------------------- >>>>> 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 >>>>> >>>> --------------------------------------------------------- >>>> 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(8 >>>> >>> --------------------------------------------------------- >>> 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(8 >>> > > -- Matthew A Perosi Computer Engineer Senior Web Developer SEO Analyst & Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Service: 973.413.8213 Training: 973.413.8214 Fax: 973.413.8217 http://www.psiprime.com --------------080801080601070308030006 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I do see my confusion with all of this now too.

Although the docs do say "Filemaker" I'm not a filemaker user and therefore would not know there as a difference.

Also, I've never used the .db format with the first row as the field names.  All my previous attempts were with the .hdr file.

So I should assume that the CSV format only works when self contained within the .db file only. 

As for the issues Stuart mentioned with numerical and text fields that include commas... I've had the same exact issues and also developed my own cleaning methods.

I don't have the time right now to test this on my own, but I will watch this thread with curiosity.  I have a large project coming up in August that will need the CSV import format and I'll be ecstatic if this works.

I'll report back at a later time with my particular findings.

Thanks for covering this topic again.... too bad no one mentioned the details below 5 years ago.

Matt

christophe.billiottet@webdna.us wrote: 
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.  

- chrisBegin forwarded message:  
From: christophe.billiottet@webdna.usDate: June 22, 2010 22:40:02 GMT-03:00To: <talk@webdna.us>Subject: Re: [WebDNA] Fails to recognize comma-separated dbReply-To: <talk@webdna.us>Sorry, i cannot reproduce: do you follow the format explained at http://www.webdna.us/database-format.dna?for instance----------------------------------------------------------------name,address,city,state,zip"Grant","1180 Central Ave","San Marcos","CA","92079""PCS","11770 Bernardo Plaza Court","San Diego","CA","92128"----------------------------------------------------------------Here a small example:- chris============================WebDNA Software Corporation16192 Coastal HighwayLewes, DE 19958On Jun 22, 2010, at 22:06, Stuart Tremain wrote:    
Me too ......RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 23/06/2010, at 10:30 AM, christophe.billiottet@webdna.us wrote:      
Anyone with the same problem Ken found?- chris============================WebDNA Software Corporation16192 Coastal HighwayLewes, DE 19958On Jun 22, 2010, at 21:24, Kenneth Grome wrote:        
Well, i have no idea: it is the first time i hear someone speaking about such a problem. As far as i know, WebDNA started to read comma-separated databases in 1997, this specific code has not been changed since then.            
Since it no longer works the way it did in 1997, maybe now is a good time to remove the part of webdna's description that says it can open and read comma-delimited db's without modification.Sincerely,Kenneth Grome---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288          
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category(8        
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category(8      
  

-- Matthew A PerosiComputer EngineerSenior Web DeveloperSEO Analyst & EducatorPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Service:   973.413.8213Training:  973.413.8214Fax:       973.413.8217http://www.psiprime.com
--------------080801080601070308030006-- 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)
This is a multi-part message in MIME format. --------------080801080601070308030006 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I do see my confusion with all of this now too. Although the docs do say "Filemaker" I'm not a filemaker user and therefore would not know there as a difference. Also, I've never used the .db format with the first row as the field names. All my previous attempts were with the .hdr file. So I should assume that the CSV format only works when self contained within the .db file only. As for the issues Stuart mentioned with numerical and text fields that include commas... I've had the same exact issues and also developed my own cleaning methods. I don't have the time right now to test this on my own, but I will watch this thread with curiosity. I have a large project coming up in August that will need the CSV import format and I'll be ecstatic if this works. I'll report back at a later time with my particular findings. Thanks for covering this topic again.... too bad no one mentioned the details below 5 years ago. Matt christophe.billiottet@webdna.us wrote: > 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. > > > ------------------------------------------------------------------------ > > > > - chris > > > > > Begin forwarded message: > > >> From: christophe.billiottet@webdna.us >> Date: June 22, 2010 22:40:02 GMT-03:00 >> To: >> Subject: Re: [WebDNA] Fails to recognize comma-separated db >> Reply-To: >> >> Sorry, i cannot reproduce: do you follow the format explained at http://www.webdna.us/database-format.dna? >> >> for instance >> >> ---------------------------------------------------------------- >> name,address,city,state,zip >> "Grant","1180 Central Ave","San Marcos","CA","92079" >> "PCS","11770 Bernardo Plaza Court","San Diego","CA","92128" >> ---------------------------------------------------------------- >> >> >> >> Here a small example: >> >> >> - chris >> ============================ >> WebDNA Software Corporation >> 16192 Coastal Highway >> Lewes, DE 19958 >> >> On Jun 22, 2010, at 22:06, Stuart Tremain wrote: >> >> >>> Me too ...... >>> >>> >>> Regards >>> >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>> >>> >>> >>> >>> On 23/06/2010, at 10:30 AM, christophe.billiottet@webdna.us wrote: >>> >>> >>>> Anyone with the same problem Ken found? >>>> >>>> - chris >>>> ============================ >>>> WebDNA Software Corporation >>>> 16192 Coastal Highway >>>> Lewes, DE 19958 >>>> >>>> On Jun 22, 2010, at 21:24, Kenneth Grome wrote: >>>> >>>> >>>>>> Well, i have no idea: it is the first time i hear someone speaking about such a problem. As far as i know, WebDNA started to read comma-separated databases in 1997, this specific code has not been changed since then. >>>>>> >>>>> Since it no longer works the way it did in 1997, maybe now is a good time to remove the part of webdna's description that says it can open and read comma-delimited db's without modification. >>>>> >>>>> Sincerely, >>>>> Kenneth Grome >>>>> --------------------------------------------------------- >>>>> 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 >>>>> >>>> --------------------------------------------------------- >>>> 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(8 >>>> >>> --------------------------------------------------------- >>> 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(8 >>> > > -- Matthew A Perosi Computer Engineer Senior Web Developer SEO Analyst & Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Service: 973.413.8213 Training: 973.413.8214 Fax: 973.413.8217 http://www.psiprime.com --------------080801080601070308030006 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I do see my confusion with all of this now too.

Although the docs do say "Filemaker" I'm not a filemaker user and therefore would not know there as a difference.

Also, I've never used the .db format with the first row as the field names.  All my previous attempts were with the .hdr file.

So I should assume that the CSV format only works when self contained within the .db file only. 

As for the issues Stuart mentioned with numerical and text fields that include commas... I've had the same exact issues and also developed my own cleaning methods.

I don't have the time right now to test this on my own, but I will watch this thread with curiosity.  I have a large project coming up in August that will need the CSV import format and I'll be ecstatic if this works.

I'll report back at a later time with my particular findings.

Thanks for covering this topic again.... too bad no one mentioned the details below 5 years ago.

Matt

christophe.billiottet@webdna.us wrote: 
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.  

- chrisBegin forwarded message:  
From: christophe.billiottet@webdna.usDate: June 22, 2010 22:40:02 GMT-03:00To: <talk@webdna.us>Subject: Re: [WebDNA] Fails to recognize comma-separated dbReply-To: <talk@webdna.us>Sorry, i cannot reproduce: do you follow the format explained at http://www.webdna.us/database-format.dna?for instance----------------------------------------------------------------name,address,city,state,zip"Grant","1180 Central Ave","San Marcos","CA","92079""PCS","11770 Bernardo Plaza Court","San Diego","CA","92128"----------------------------------------------------------------Here a small example:- chris============================WebDNA Software Corporation16192 Coastal HighwayLewes, DE 19958On Jun 22, 2010, at 22:06, Stuart Tremain wrote:    
Me too ......RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 23/06/2010, at 10:30 AM, christophe.billiottet@webdna.us wrote:      
Anyone with the same problem Ken found?- chris============================WebDNA Software Corporation16192 Coastal HighwayLewes, DE 19958On Jun 22, 2010, at 21:24, Kenneth Grome wrote:        
Well, i have no idea: it is the first time i hear someone speaking about such a problem. As far as i know, WebDNA started to read comma-separated databases in 1997, this specific code has not been changed since then.            
Since it no longer works the way it did in 1997, maybe now is a good time to remove the part of webdna's description that says it can open and read comma-delimited db's without modification.Sincerely,Kenneth Grome---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288          
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category(8        
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usold archives: http://dev.webdna.us/TalkListArchive/Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category(8      
  

-- Matthew A PerosiComputer EngineerSenior Web DeveloperSEO Analyst & EducatorPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Service:   973.413.8213Training:  973.413.8214Fax:       973.413.8217http://www.psiprime.com
--------------080801080601070308030006-- "Psi Prime Inc, Matthew A Perosi "

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:

Emailer Error Question (1998) Multiple catalog databases and showcart (1997) [WebDNA] [announce] Marketing new hire (2009) No Line Breaks from OSX server (more) (2002) WebDNA Speed Test (2008) Emailer Problem (1999) WebCat2b12plugin - [search] is broken ... not! (1997) [WebDNA] WebDNA and simple password systems (2009) Template not found error messages (1997) [isfolder] and [filename] (1997) Still online from NY (2003) WC TableGrinder (1997) Pithy questions on webcommerce & siteedit (1997) all records returned. (1997) writing cart to db (1998) Sorting by date (1997) WebDNA & Suse Linux (2004) Help! WebCat2 bug (1997) WebCatalog for Mac 2.0.1 Released (1997) Help! WebCat2 bug (1997)