[RESOLVED] Design question.
I'll try to give you a short explanation of my problem; if you need more information, please feel free to ask here, and I'll provide it asap.
I'm basically implementing a user-interface on a database, that will allow the user to interact with the database without actually having access to it. There are 4 major tables of information:
* Persons (containing basic information about Persons - BIG)
* Clubs (containing basic information about Clubs - SMALL)
* Members (joining Persons and Clubs to keep track of memberships - BIG)
* Logins (keeping track of Member visits to Clubs - ENORMOUS)
Usually when implementing such systems, I'll make a main window with a tab-strip for each part (table in this case) of the data. Each tab-strip will contain a list of commands available on the data and a readonly datagrid for displaying searchresults and allowing for selections to be edited/deleted through pop-up windows. My concern is though, that several datagrids containing huge amounts of information, will take it's toll on the system ressources, and perhaps my approach should be different in this case. I'd like inputs as to how you usually implement such systems.
Further info:
* Persons - approximately 120 bytes information each ~ 10,000 entries
* Clubs - approximately 40 bytes information each ~ 25 entries
* Members - approximately 20 bytes information each ~ 3,000 entries
* Logins - approximately 30 bytes information each ~ 200,000+ entries
All tables are indexed on one or more fields to allow for fast searching.
The Login table will never be used in it's entirity but the other tables may.
Any/all inputs appreciated - even if you never implemented anything similar.
[The core of the question is probably whether a datagrid will load assigned query-data in it's entirity or retrieve it on an 'as-needed' basis.]
Regards Tom