Is it OK to have several instances of the same recordsets to perform different purposes in a database app?
Here's what I'm trying to do:
1. Show all info 1 record at a time (from several related tables) in a view
2. Allow users to browse each separate table & set filters to find various sets of records
SHould I create different recordsets in the document & give them to each view as they are needed? SInce this is an MDI app, users can switch back & forth between windows at any time.
Also, does anyone have any generic filter-setting code? Right now I have a hard-coded dialog for each table. It seems redundant. I'm wondering if there is a generic class that could read a table structure & present it to users for filtering.