Transaction Tracking

I'm currently working on a database layout for a program that handles accommodations at resort destinations. The issue that I'm having at this point is tracking transactions on different inquiries. For example, while a unit can have multiple prices per night based on different criteria, I need to keep all of that information in a transactions table. The transactions table must keep track of all the quoted prices per night and total number of nights is a variable (eg. one can stay 3 nights or 30) and all the nights can have differing prices. The immediate solution I see is to keep a lookup table that will have a one to many relationship to different tables that keep track of each night's price. This is a faulty design which will repeat data and be hard to maintain since the possibility of having an ulimited number of tables exists... well that just sucks... so do any of you have any suggestions for me?

Dan Received on Sun Jul 01 2001 - 20:03:54 CEST