sounds good to me. sql2005 has an xml data type.. I'll play around with it and see what I can come up with
been messin around with it here & there thru the day. If you want to move the discussion to email, we can certainly do so, or keep it here in the forum.
I'm thinking about putting the the recipe data in the SQL table. At least for my website, I have limited space for files and for db data. BUT in putting the xml recipe files in the database, we eleminate the issue of users uploading files with the same name (more so since beersmith's default is recipes.xml). We (imho) also have better control over who can access what without having to touch file system permissions. let me know what you think. I have a skeleton of a system in place and working. Currently I have name, recipe name, style/sub-style ( I split apart like 6 and A,B,C etc to make it easier to search), and I am storing the XML in the database. Tomorrow I'm going to work on just pulling the info from the xml file that way the person uploading a recipe wouldn't have to type the info in. I can just extract it from the xml.
so currently you have to export the recipes from beersmith, go to the website, log-in, fill in the small form and browse to the xml file, click submit and you're done. still have search, etc to go.
I am also working on this with MSSQL 2005 and ASP. I guess it depends a lot on where the files are hosted whether it would make more sense to move to perl/php or whatever
Paul...