>Hi - as I am fairly new I often wonder whether what I am doing is the right way to do things (often I have no idea what to do!) or at least an acceptable way. My current question is about a application I am currently developing - nothing special really - it's a customer database which records orders, deliveries and invoices against each customer. The client wants to report on any given date range so my current approach is to have one table the records each and every transaction. My only worry is that this table over a period of time is just going to get huge and really slow.
>Can anyone suggest alternatives or better ways of handling this sort of thing as I am sure it is a common issue.
>
>Thanks

How big do you think it will get? If the table is properly Indexed (all fields you will be querying on) then Rushmore should take care of speed of inquire problems. I have an application that has 13,000 parents, 500,000 children, and 5 million grand children and speed of querying is no problem. Just ensure that you normalize your table and index on anything you will be using to query on.