Re: FileMaker and WebCat

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 23135
interpreted = N
texte = >Probably a very dumb question... > >One of my clients runs their back office on FileMaker from where I get the >data to drive their website - running out of Webstar and WebCatalog. > >I have a pretty clunky way of transferring this data and I wonder if anyone >has a better idea? > >I export out of FileMaker into a tab delimited text file, which I then open >in a text editor where I add a header containing the field names. I save >this as the data table which WebCatalog reads. > >FileMaker does not appear to have any export options which can be read >directly by WebCatalog without this process. > >Julian ClaytonWell, I have been working with a similar problem myself. I have a huge multiuser Filemaker solution that is exporting tab-sep .db files. I have first set up a script in Filemaker that exports all the fieldsI I need (at the time being). Then this tab sep file is imported into another filemaker database that has all the hdr names set at the first record). All imported files will be added from record 2 to 5000 etc. Then this is again exported to a tab-sep file with the correct name set to the file and moved by retrospect to the webservers directory for the .db files. After the export is done, I have a script that searches for the record that has the word SKU set in the SKU field (all other values for the proper records are 13charachter EAN-numbers parsed with a countryspecific code (.uk,.de, etc so there will be no risk of mixing header data with product data). Then the script omits the found record (actually the starting record) and deletes all other records. This way this database is cleaned for everything except the header data. This procedure has run several times each day for 8 months now without any trouble. Associated Messages, from the most recent to the oldest:

    
  1. Re: FileMaker and WebCat (PCS Technical Support 1999)
  2. Re: FileMaker and WebCat (Stein Grebstad 1999)
  3. Re: FileMaker and WebCat - .hdr OK Merge not OK (Julian Clayton 1999)
  4. Re: FileMaker and WebCat - .hdr OK Merge not OK (PCS Technical Support 1999)
  5. Re: FileMaker and WebCat - .hdr OK Merge not OK (John Hill 1999)
  6. Re: FileMaker and WebCat - .hdr OK Merge not OK (Julian Clayton 1999)
  7. Re: FileMaker and WebCat (Larry Hewitt 1999)
  8. Re: FileMaker and WebCat (Christer Olsson 1999)
  9. Re: FileMaker and WebCat (Sandra L. Pitner 1999)
  10. RE: FileMaker and WebCat (Edouard Janssens 1999)
  11. RE: FileMaker and WebCat (Edouard Janssens 1999)
  12. FileMaker and WebCat (Julian Clayton 1999)
>Probably a very dumb question... > >One of my clients runs their back office on FileMaker from where I get the >data to drive their website - running out of Webstar and WebCatalog. > >I have a pretty clunky way of transferring this data and I wonder if anyone >has a better idea? > >I export out of FileMaker into a tab delimited text file, which I then open >in a text editor where I add a header containing the field names. I save >this as the data table which WebCatalog reads. > >FileMaker does not appear to have any export options which can be read >directly by WebCatalog without this process. > >Julian ClaytonWell, I have been working with a similar problem myself. I have a huge multiuser Filemaker solution that is exporting tab-sep .db files. I have first set up a script in Filemaker that exports all the fieldsI I need (at the time being). Then this tab sep file is imported into another filemaker database that has all the hdr names set at the first record). All imported files will be added from record 2 to 5000 etc. Then this is again exported to a tab-sep file with the correct name set to the file and moved by retrospect to the webservers directory for the .db files. After the export is done, I have a script that searches for the record that has the word SKU set in the SKU field (all other values for the proper records are 13charachter EAN-numbers parsed with a countryspecific code (.uk,.de, etc so there will be no risk of mixing header data with product data). Then the script omits the found record (actually the starting record) and deletes all other records. This way this database is cleaned for everything except the header data. This procedure has run several times each day for 8 months now without any trouble. Stein Grebstad

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:

Review comparison by PC Magazine: Open for On-line Business (1997) Strange intermittent WebDNA problems (2008) RE: Redirect (1998) an easy one... (2000) CC and Europe (1999) is your webDNA site 'froogle' ready ??? (2003) Date summarising (2005) Instructions for Digest (1997) form data submission gets truncated (1997) DB permission issues (2004) Register First (2000) [UPPERCASE] (1997) Web Delivery Page concept (1997) Sending E-mail (1997) Grep Ampersands (2008) Calendar using WebCatalog? (1997) Robert Minor duplicate mail (1997) Not reading code (1997) Resume Catalog ? (1997) GrandTotal not right (1997)