Gustav Brock
gustav at cactus.dk
Wed Feb 12 08:37:00 CST 2003
Hi Andy Yes, you could do some copying of a master but that would add some level of bloat. But it is a solution. Another possibility is to write protect the database file itself which can be done if you don't write to internal tables or modify objects. A third option is to apply Jet security and remove design rights for the report. That is very effective; however, if the user changes printer settings and close the report and answer yes to save the changes, a small box appears prompting for a new name the report can be saved as. Not very elegant. So I'm still looking for the "right" solution ... Other ideas? /gustav > Sorry Gustav. I knew my answer was an imperfect solution but hard to know what else will do. OK, here's a really off-the-wall idea. Can you, in code, create a new report as a copy of the original, > and open that? Then it wouldn't make any difference what the user did to the copy. I've never tried that and don't know if it's feasible, and bloat would probably be an issue. Just trying to think > laterally. And on a Friday thinking in any direction's hard enough :-( > Andy Lacey > http://www.minstersystems.co.uk > Yes, but that wouldn't help if the user simply closes the preview > window. > My thought was to set warnings off but neither that doesn't help as > the default for the messagebox is Yes to save the changes. > Other ideas? > /gustav >> Can you give the user a button on the toolbar to use for closing? If so >> you can issue a Close with acSaveNo as the second parameter. >> Andy Lacey >> http://www.minstersystems.co.uk >>> If you preview a report and allow the user to adjust printer >>> settings, how can you - when the user does so, prints, and >>> closes the report - remove, ignore or cancel the message box >>> asking if the report should be saved? >>> >>> I want the report to remain unchanged.