Royal Presence
Board Regular
- Joined
- Feb 27, 2003
- Messages
- 92
Hi,
I am still working on my tree view. Thank you very much. I will get this concept fully one day. Right now, I am just using buttons and hyperlinks for the main menus.
Anyway, I have a new question:
Is this a good idea or a bad idea? I have an order processing database that has experienced several design changes. It is working lovely for the data entry people, and okay for the viewers, I'm working on that now. However, I want to take 2004 orders and put them all in a separate db when the end of this calendar year occurs and then just keep our
clients and addresses, etc., same table structure, order form, etc., for new 2005 orders. Then I can just refer via linking when people need to reference any history.
Sounds like a good idea and will help with production week dating, but does it make sense or am I on the wrong path.
Thanks.
Paula
I am still working on my tree view. Thank you very much. I will get this concept fully one day. Right now, I am just using buttons and hyperlinks for the main menus.
Anyway, I have a new question:
Is this a good idea or a bad idea? I have an order processing database that has experienced several design changes. It is working lovely for the data entry people, and okay for the viewers, I'm working on that now. However, I want to take 2004 orders and put them all in a separate db when the end of this calendar year occurs and then just keep our
clients and addresses, etc., same table structure, order form, etc., for new 2005 orders. Then I can just refer via linking when people need to reference any history.
Sounds like a good idea and will help with production week dating, but does it make sense or am I on the wrong path.
Thanks.
Paula