I was asked yesterday to secure the backend mdb from users being able to edit records by opening the backend mdb file.Obviously, this must include the frontend linked tables and queries. After researching I decided to go with simply hiding them in the database window. I am writing a VB6 program that uses ADOX to set the Hidden Table property of the TABLEs, LINKs, and VIEWs. The problem is that when I run the code to unhide these objects, the VIEWs do not appear in the tables collection of the catalog as they did when the Hidden Table property was False! The TABLEs and LINKs DO appear in the collection and they are being reset to False. I’m working now at home where I have Access2002. At the office I have Access2000. The customer uses Access2000. The Views collection has a count of 0 (even when the query is visable). My plan at present is to export the queries as a backup and then Hide them.
I suppose I could disable the shift key and hide the db window, but someone could still createnew links for a new mdb. This flaw may be acceptable, I’ll have to check. The customer, at present, won’t be paying for this and basically, if a user won’t know how to circumvent this. I’m sorry but I’m in contact with a co-worker who supports this customer and I’m not completely up on the exact problem or requirements as yet. Even with user-security, how do you prevent a user who has permissions on a table from editing it directly?
What’s the problem with my ADOX app?