Change form properties or create a new form?

[jimlee]

Hi All,

I have various forms in my db which display recordsets and have 'multi' filters (combo boxes) in the footer so you can search for just about any combination of fields. The combo boxes get their info from the forms recordset via SQL statements

The information on the forms can be Verified by the user and then, when the form is closed all verified records are sent to an archive table.

I want to be able to view and filter these archived records in exactly the same way as the live records.

I have tried using the same form but changing it's record source which works fine. I can also provide a second set of combo filters (in which the sql statement for their row source is looking at the archive table) or change the row sources of the combo filters programmatically. In short this can be done and everything works.

Or...
I can just copy the forms and make new archive forms in the db and just open them when you need them. (this means I have twice as many forms stored in my db) but there will be no need to change all recordsources etc every time in the code.

I can make both methods work, but I was wandering if there's any major reasons for doing things one way or another, is it just personal preference? feedback and opinions appreciated.

jimlad

 

[MD5150]

It's usually best to try and avoid duplicate forms in your database, which helps avoid double work. Personal preference can be a part of development, but the major reason for one method of development being better than the other should depend on your project requirements, and what would make your database the most reliable, efficient, and useful...along with many other factors.

I'd say using one form with an option group for viewing both current and archive data would be nice.

Hope this helps,

Mike Dorthick