Is there a good way to encrypt end-user report files/templates to make it so they can't be opened by another end-user (or developer for that matter)? Any tips welcome.
Guess I need to clarify. What I'm wondering is if there is some way to control the save to file process so that the file is a proprietary format. There is an event to get control over the entire save process (OnCustomOpenDoc/OnCustomSaveDoc), but I think that is a bit much. I guess what I'm looking for is an event for save that would allow me to alter the file in memory before it is written to disk and then write the file, doing the reverse on a load event. Anything like that out there? Or maybe I could call something from inside OnCustomSaveDoc to get the file ready to save, then alter it?
Comments
use a database that supports encryption.
--
regards,
Chris Ueberall;
Guess I need to clarify. What I'm wondering is if there is some way to
control the save to file process so that the file is a proprietary format.
There is an event to get control over the entire save process
(OnCustomOpenDoc/OnCustomSaveDoc), but I think that is a bit much. I guess
what I'm looking for is an event for save that would allow me to alter the
file in memory before it is written to disk and then write the file, doing
the reverse on a load event. Anything like that out there? Or maybe I
could call something from inside OnCustomSaveDoc to get the file ready to
save, then alter it?
Thanks,
Jim
I think OnCustomOpenDoc/OnCustomSaveDoc are going to be your best bet.
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com