M
matt
Is there a way to hide a table from user view in an Access
2000 db? any advice is greatly appreciated. thanks,
matt
2000 db? any advice is greatly appreciated. thanks,
matt
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Rick B
Right-click and set it to hidden. If your users have their Access settings
to not view hidden files, then you are all set.
Rick B
to not view hidden files, then you are all set.
Rick B
G
Guest
Then my next question would be if it is possible to
restrict users from going into tools, options and changing
the "view hidden objects" property. Am using Access 2000
User-level security.
restrict users from going into tools, options and changing
the "view hidden objects" property. Am using Access 2000
User-level security.
J
Jamie Richards
Rick,
Consider utilising the security provided by Access to secure your
application. You can also include some code which sets certain application
options using the GetOption and SetOption methods (refer to Access help for
more info on that). You could run this code on application startup so that
the Access settings you want are set for your users. I sometimes use this
feature by first reading the users Access settings into a table at startup
so I can reset them when the user quits my app. In conjunction with this
you would need to ensure that you replace the standard toolbars with a set
of your own and that you include code which disables the (Shift) bypass key.
Finally, if you can, distribute your app as an MDE (or ADE if it's a SQL
Server Project), it will remove the source code, preventing savvy users from
altering anything they shouldn't.
Jamie
Consider utilising the security provided by Access to secure your
application. You can also include some code which sets certain application
options using the GetOption and SetOption methods (refer to Access help for
more info on that). You could run this code on application startup so that
the Access settings you want are set for your users. I sometimes use this
feature by first reading the users Access settings into a table at startup
so I can reset them when the user quits my app. In conjunction with this
you would need to ensure that you replace the standard toolbars with a set
of your own and that you include code which disables the (Shift) bypass key.
Finally, if you can, distribute your app as an MDE (or ADE if it's a SQL
Server Project), it will remove the source code, preventing savvy users from
altering anything they shouldn't.
Jamie