> you know, you might not have to do that much work after all. you could use > MS Access to import the information into an access database. after that, you > can cut and paste the information into different tables and create > relationships. if you really want to get jiggy with it, you can then use the > upsize wizard to smack the puppy into a SQL database. so you fear of this > job being 4 weeks, turn into 4 hours. gotta love Microsoft (oops, did i say > that).
Simply upgrading to importing to MS Access or SQL Server may help performance, but it won't normalize it. Also, if you have a large flat file, cutting and pasting may not be an option. Also, because of the good possibility for human error, you would probably want to simply compile the tables with queries instead of doing a cut and paste. I looked for "normalize database" on Google and it seemed to have some good stuff. I found an article on SQL Server magazine that explains normal forms. It might be a little advanced though: http://www.sqlmag.com/Articles/Index.cfm?ArticleID=4887&pg=1 Eric, if you'd like, you can e-mail me off-list at [EMAIL PROTECTED] and I'd be glad to help you figure out the normalization of your flat file. Ben Johnson Hostworks, Inc. ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

