I've got a client sight that wants to insure that any reports
distributed to the user can not be changed by the user (unless they
knowingly hack around).
Now I used Access95 to write reports for a VB5 application instead of
Crystal (I hate crystal). But if I distribute the .mdb file, if the user
has full-blown Access, they can change the report.
Does anyone know:
1) how to protect just the reports/queries from being tampered with
2) is there anyway to "compile"/.ect those reports into something other
than a .mdb file (I know that's a long shot, but hey!)
Thanks for any help - hope everyone has a good monday ;-)