I'm not sure how to describe it other than it's a pseudo multi user environment that is open but I want to have some control over a few things such as this report.
Basically, the report is a generic base that different headers are added to on the fly. If a user happens to save their iteration of the report it starts to have multiple headers. This is "bad" since the next user will now have the previous headers plus their own.
I had thought about building the entire report in VBA and generating the whole thing on the fly.....but I dont' feel like taking the time to do that and placing all the field outputs correctly...etc.
The problem is you either implement user level security or you don't. Access isn't sophisticated enough to allow ownership of one particular object without implementing some kind of security. Everyone who opens the report will have the exact same privelages you do, which is full control.
You could try playing with the DoCmd.Close method and using acSaveNo, but it's still a little risky.
Is use the OnClose event to launch a form. Since the OnClose event can't have a DoCmd statement in it, I'll force the user out to a form that will prompt them whether they REeeeeaaallly want to close the report they're working on.
I know...it's not great but I think it fits the current bill.
Thanks for the ideas.
PS- Never mind....I forgot that the OnClose event comes AFTER the save event. OH well...they'll just have to be reallly good users. Bwwwahahahah.....
you consider deploying the app front end as a distributed (ie local) copy for each user. then let them tinker to their hearts content with their own version. If they wreck the report then tough sh1t...... you may need for political reasons keep a good copy elsewhere so that they can recover from their latest cockup