Re: Switching from merge to tab delimited..(v 2.x)
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 33505
interpreted = N
texte = see belowChristopher Feyrer wrote:> >>I'm dealing with a database with hundreds of fields. This is what I did to> >>accomplish the switch:> >>> >>1. I expored the database as tab delimited from Filemaker Pro.> >>2. I created a database.hdr file from the top line with the field of the> >>previous database, replacing commas with tabs so that the fields would be> >>tab seperated. Then, I put a carriage return at the end.> >>3. I commited and closed all databases.> >> >This all sounds right, so the most important thing is to make *sure*> >the .hdr matches the actual data perfectly. You might try pulling> >the .hdr into Excel, and then pull in the data on the lines below> >that, as a means of lining everything up.> >>> I'm on a Macintosh which does not have Excel. Any other ideas as to how I> can line these fields up? BBEdit would be extremely time consuming.. can> you think of another solution that would not take as much time?filemaker pro.>>> >It's also possible you really are out of memory, so try bumping> >WebCatalog's allocation up.> >> >>Also, I'm having trouble getting rid of vertical tabs from my database.> >>What's the best way to do this (can it be avoided during export from> >>Filemaker)?> >> >WebCatalog doesn't mind vertical tabs. In fact, it recognizes them> >for what they are (soft-returns) and will output them as hard returns> >if you wrap the database field tag inside an [input] context.> >>> Eek. Does this mean I have to go into each and every page of my website> and replace all field references to [input][field][/input]??only where you want to display the contents of that field while simultaneously havingthe soft returns converted to hard ones. If you don't need that in a given spot, thendon't bother.There are> hundreds of database references in the site..this will be time consuming as> well!>> IT'll be quite frustrating if there are no alternatives.>> CJF>> Christopher Feyrer> System Administrator> FoodSpot.com> chris@foodspot.com> -------------------> PGP 6.x key available.>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list
.> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
see belowChristopher Feyrer wrote:> >>I'm dealing with a database with hundreds of fields. This is what I did to> >>accomplish the switch:> >>> >>1. I expored the database as tab delimited from Filemaker Pro.> >>2. I created a database.hdr file from the top line with the field of the> >>previous database, replacing commas with tabs so that the fields would be> >>tab seperated. Then, I put a carriage return at the end.> >>3. I commited and closed all databases.> >> >This all sounds right, so the most important thing is to make *sure*> >the .hdr matches the actual data perfectly. You might try pulling> >the .hdr into Excel, and then pull in the data on the lines below> >that, as a means of lining everything up.> >>> I'm on a Macintosh which does not have Excel. Any other ideas as to how I> can line these fields up? BBEdit would be extremely time consuming.. can> you think of another solution that would not take as much time?filemaker pro.>>> >It's also possible you really are out of memory, so try bumping> >WebCatalog's allocation up.> >> >>Also, I'm having trouble getting rid of vertical tabs from my database.> >>What's the best way to do this (can it be avoided during export from> >>Filemaker)?> >> >WebCatalog doesn't mind vertical tabs. In fact, it recognizes them> >for what they are (soft-returns) and will output them as hard returns> >if you wrap the database field tag inside an [input] context.> >>> Eek. Does this mean I have to go into each and every page of my website> and replace all field references to [input][field][/input]??only where you want to display the contents of that field while simultaneously havingthe soft returns converted to hard ones. If you don't need that in a given spot, thendon't bother.There are> hundreds of database references in the site..this will be time consuming as> well!>> IT'll be quite frustrating if there are no alternatives.>> CJF>> Christopher Feyrer> System Administrator> FoodSpot.com> chris@foodspot.com> -------------------> PGP 6.x key available.>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://search.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
John Butler
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:
Extracting URL (2007)
Signal Raised Error (1997)
errormessages.db (1997)
problem: mail changed (1997)
unable to launch acgi in WebCat (1997)
taxTotal, grandTotal (1997)
Search (1997)
WebTEN vs webSTAR (1998)
no time stamp & different times from emailer (1998)
database visibility (2000)
WebMerchant Problem (1999)
Search in 2 or more catalogs (1997)
MacOS X Server problems (2001)
WebCatalog and WebTen (1997)
converting characters in form (1997)
Append command(2) (2000)
RAM problems, [appendfile] problems (1998)
Interpreting WebDNA tags (2004)
Online reference (1997)
WC2.0 Memory Requirements (1997)