24 Aug 12 12:45
You could create Before Update or After Update events for the specific fields which should trigger a revision bump to update the revision. You'd need to store the revision in data somewhere, as well. The table you'd want to use would depend on how far down the data changes need to impact revision - if a change in the minor data is not supposed to change the revision, then it should go into the major table.
If multiple fields can impact the revision, you may just want the events to:
If the checkbox is not checked then
--bump the revision in the data
--Make sure the checkbox is checked
which would make it so that the second, third, etc. fields which are changed would do nothing.
Just make sure you have coding in place to uncheck the box if you move to a new record. If you are not committing data changes until the user performs a specific action, you can skip the entire checkbox and associated routine and just add the revision bump to that action's event.
On the reports, you may have to set the footer output to use one of your grouping footers instead of the page footer, or set up a query to pull the latest revision for each item and use a DLookup to connect to the correct one.
I hope this is helpful.
Cheryl dc Kern