Re: [WebDNA] Fails to recognize comma-separated db
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105394
interpreted = N
texte = --Apple-Mail-2-544159637Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiKenThe problem with ONLY commas is that text is not validated, ie if the =value is Tremain, Stuart then it will get split into two different =fields.If it were ,"Tremain, Stuart", then it would be held in one field as =intended.I had great problems with a client that sent files that only validated =the text fields (put "" around the text) and not the number fields so I =was getting a file that looked like this:1001,"text field 01","txt field 02","txt field 03, with a =comma",256378,76534,"","",,I had to undergo a big cleaning process to get it right. See solution =below=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D[TABLE name=3DCLEAN01&fields=3DFROM,TO]%2C%20=09[/TABLE][TABLE name=3DCLEAN02&fields=3DFROM,TO]%22%2C%22|%22=09%2C|[/TABLE][TABLE name=3DCLEAN03&fields=3DFROM,TO]|%09[/TABLE][Table =name=3DFocusReports&fields=3DDirectDebitId,CustNo,StoreNo,Title,FirstName,=LastName,Address1,Suburb2,City,State,PostCode,Email,DOB,Sex,RightSkuNo,Lef=tSkuNo,RightQty,LeftQty,HealthFund,DeliveryDt,SaleAmt,Discount,RxIssueDt,R=xExpiryDt,ReplnFreq,DrNo,DrTitle,DrLastName,DrFirstName,DeliverTo,DlvyAddr=1,DlvySuburb2,DlvyCity,DlvyState,DlvyPcode,PayrollNo1,PayrollNo2,HomePhone=,WorkPhone,MobilePhone,Country,Brand,InclSolution][convertchars table=3DCLEAN03][grep =search=3D,&replace=3D][unurl][convertwords table=3DCLEAN02][ConvertWords =table=3DCLEAN01][Middle StartAfter=3DInclSolution][url][Include =file=3DUPLOADED-FILE-HERE][/url][/Middle][/ConvertWords][/convertwords][/u=nurl][/grep][/convertchars][/Table]=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DRegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 24/06/2010, at 1:24 PM, Kenneth Grome wrote:> 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).--Apple-Mail-2-544159637Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiKen
The problem with ONLY commas is that text is =not validated, ie if the value is Tremain, Stuart then it will get split =into two different fields.
If it were =,"Tremain, Stuart", then it would be held in one field as =intended.
I had great problems with a client =that sent files that only validated the text fields (put "" around the =text) and not the number fields so I was getting a file that looked like =this:
1001,"text field 01","txt field 02","txt =field 03, with a comma",256378,76534,"","",,
I =had to undergo a big cleaning process to get it right. See solution =below
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=
[TABLE name=3DCLEAN01&fields=3DFROM,TO]
%2C%20=
[/TABLE]
[TABLE =name=3DCLEAN02&fields=3DFROM,TO]
%22%2C%22=|
%22
%2C=|
[/TABLE]
[TABLE =name=3DCLEAN03&fields=3DFROM,TO]
|%09
[/TABLE]
[Table =name=3DFocusReports&fields=3DDirectDebitId,CustNo,StoreNo,Title,FirstN=ame,LastName,Address1,Suburb2,City,State,PostCode,Email,DOB,Sex,RightSkuNo=,LeftSkuNo,RightQty,LeftQty,HealthFund,DeliveryDt,SaleAmt,Discount,RxIssue=Dt,RxExpiryDt,ReplnFreq,DrNo,DrTitle,DrLastName,DrFirstName,DeliverTo,Dlvy=Addr1,DlvySuburb2,DlvyCity,DlvyState,DlvyPcode,PayrollNo1,PayrollNo2,HomeP=hone,WorkPhone,MobilePhone,Country,Brand,InclSolution]
[convertchars table=3DCLEAN03][grep =search=3D,&replace=3D][unurl][convertwords =table=3DCLEAN02][ConvertWords table=3DCLEAN01][Middle =StartAfter=3DInclSolution][url][Include =file=3DUPLOADED-FILE-HERE][/url][/Middle][/ConvertWords][/convertwords][/u=nurl][/grep][/convertchars]
[/Table]
=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D
Regards
Stuart Tremain
IDFK =Web Developments
AUSTRALIA
=div>
On 24/06/2010, at 1:24 PM, Kenneth Grome wrote:
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).
=--Apple-Mail-2-544159637--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-2-544159637Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiKenThe problem with ONLY commas is that text is not validated, ie if the =value is Tremain, Stuart then it will get split into two different =fields.If it were ,"Tremain, Stuart", then it would be held in one field as =intended.I had great problems with a client that sent files that only validated =the text fields (put "" around the text) and not the number fields so I =was getting a file that looked like this:1001,"text field 01","txt field 02","txt field 03, with a =comma",256378,76534,"","",,I had to undergo a big cleaning process to get it right. See solution =below=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D[TABLE name=3DCLEAN01&fields=3DFROM,TO]%2C%20=09[/TABLE][TABLE name=3DCLEAN02&fields=3DFROM,TO]%22%2C%22|%22=09%2C|[/TABLE][TABLE name=3DCLEAN03&fields=3DFROM,TO]|%09[/TABLE][Table =name=3DFocusReports&fields=3DDirectDebitId,CustNo,StoreNo,Title,FirstName,=LastName,Address1,Suburb2,City,State,PostCode,Email,DOB,Sex,RightSkuNo,Lef=tSkuNo,RightQty,LeftQty,HealthFund,DeliveryDt,SaleAmt,Discount,RxIssueDt,R=xExpiryDt,ReplnFreq,DrNo,DrTitle,DrLastName,DrFirstName,DeliverTo,DlvyAddr=1,DlvySuburb2,DlvyCity,DlvyState,DlvyPcode,PayrollNo1,PayrollNo2,HomePhone=,WorkPhone,MobilePhone,Country,Brand,InclSolution][convertchars table=3DCLEAN03][grep =search=3D,&replace=3D]
[unurl][convertwords table=3DCLEAN02][ConvertWords =table=3DCLEAN01][Middle StartAfter=3DInclSolution]
[url][Include =file=3DUPLOADED-FILE-HERE][/url][/Middle][/ConvertWords][/convertwords][/u=nurl][/grep][/convertchars][/Table]=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DRegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 24/06/2010, at 1:24 PM, Kenneth Grome wrote:> 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).--Apple-Mail-2-544159637Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiKen
The problem with ONLY commas is that text is =not validated, ie if the value is Tremain, Stuart then it will get split =into two different fields.
If it were =,"Tremain, Stuart", then it would be held in one field as =intended.
I had great problems with a client =that sent files that only validated the text fields (put "" around the =text) and not the number fields so I was getting a file that looked like =this:
1001,"text field 01","txt field 02","txt =field 03, with a comma",256378,76534,"","",,
I =had to undergo a big cleaning process to get it right. See solution =below
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=
[TABLE name=3DCLEAN01&fields=3DFROM,TO]
%2C%20=
[/TABLE]
[TABLE =name=3DCLEAN02&fields=3DFROM,TO]
%22%2C%22=|
%22
%2C=|
[/TABLE]
[TABLE =name=3DCLEAN03&fields=3DFROM,TO]
|%09
[/TABLE]
[Table =name=3DFocusReports&fields=3DDirectDebitId,CustNo,StoreNo,Title,FirstN=ame,LastName,Address1,Suburb2,City,State,PostCode,Email,DOB,Sex,RightSkuNo=,LeftSkuNo,RightQty,LeftQty,HealthFund,DeliveryDt,SaleAmt,Discount,RxIssue=Dt,RxExpiryDt,ReplnFreq,DrNo,DrTitle,DrLastName,DrFirstName,DeliverTo,Dlvy=Addr1,DlvySuburb2,DlvyCity,DlvyState,DlvyPcode,PayrollNo1,PayrollNo2,HomeP=hone,WorkPhone,MobilePhone,Country,Brand,InclSolution]
[convertchars table=3DCLEAN03][grep =search=3D,&replace=3D]
[unurl][convertwords =table=3DCLEAN02][ConvertWords table=3DCLEAN01][Middle =StartAfter=3DInclSolution]
[url][Include =file=3DUPLOADED-FILE-HERE][/url][/Middle][/ConvertWords][/convertwords][/u=nurl][/grep][/convertchars]
[/Table]
=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D