If there's a fixed additional rate for weekday/weekend price differences, you could always reference a 3rd table with a list of day types (1-7) and price differences. When calling the table, you could run the date through a compound math expression to find out which day of the week it was add the additional amount appropriately. Or you could reference a fourth table with a list of dates with this additional fee. In my opinion, people make too much of a big deal out of really long one-to-one relationship single-table DBs. Multiple tables or no, buy the expensive software or freebie it, we're really talking about milliseconds here, people. Once again, my two cents. But I guess that's why they're paying me those two cents - to save a few milliseconds. Hope something I said helped. Happy Tuesday,
----------------------------------- Jeff McCabe GIS Technician City of Hurst [EMAIL PROTECTED] (817) 788-7082 >>> [EMAIL PROTECTED] 7/24/2006 6:13 pm >>> I am working on building a small hotel availability application. Anyone have any experience with this? I am struggling with the best way to set up the database for the available dates / rates. There is a case where each day is priced and there is a case where the weekend and weekday rates are different. Any thoughts on how the database could be set up most efficiently? I was thinking that I would have a rates table which would have a rate for each day of the year. This would obviously be a large table once more and more hotels were added to the database. Any thoughts? Thank you! _______________________________________________ Reply to DFWCFUG: [email protected] Subscribe/Unsubscribe: http://lists1.safesecureweb.com/mailman/listinfo/list List Archives: http://www.mail-archive.com/list%40list.dfwcfug.org/ http://www.mail-archive.com/list%40dfwcfug.org/ DFWCFUG Sponsors: www.HostMySite.com www.teksystems.com/
