T
tracktraining
Hi All,
can queries be hidden from the end users?
Thanks,
Tracktraining
can queries be hidden from the end users?
Thanks,
Tracktraining
tracktraining said:can queries be hidden from the end users?
Dirk Goldgar said:Depends how clever they are. You can set the query as hidden, so it won't
appear in the database window (or Nav Pane, for A2007) unless they set their
View options to show hidden objects. You could prefix the query name with
"USys", which would keep it from appearing in the database window unless
they have their View options set to show system objects.
--
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)
Graham Mandeno said:Hi TrackTraining
The best way to hide objects from users is to hide the database window and
disable the F11 key.
If you really want to hide individual objects but show the database window,
then right-click on the object and choose "Properties". You will see a
"Hidden" checkbox there.
Note that the user can still show hidden objects by going to Tools>Options.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
tracktraining said:Hi All,
can queries be hidden from the end users?
Thanks,
Tracktraining
tracktraining said:Do you know if i can control the disable of F11 key via code?
Example: if username is equal to admin, then allow for F11 key to be
enabled else disable F11.
If i disable F11 all together then even the admin can't have access to the
tables, queries, forms, and reports .... which would cause a lot of
problems
for future updates.
Thanks,
Tracktraining
--
Learning
Graham Mandeno said:Hi TrackTraining
The best way to hide objects from users is to hide the database window
and
disable the F11 key.
If you really want to hide individual objects but show the database
window,
then right-click on the object and choose "Properties". You will see a
"Hidden" checkbox there.
Note that the user can still show hidden objects by going to
Tools>Options.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Hi All,
can queries be hidden from the end users?
Thanks,
Tracktraining
Graham Mandeno said:Unfortunately the database properties that control startup options do not
take effect until the next time the database is opened.
I would suggest the version of your database you release for production
should be different from the one you are developing. When you are ready to
release a new version, copy the development database (or even better, make
an MDE) and set the startup option properties on the copy.
Of course, you can always show the database window using code. You could
have a command button on your main form that displays the database window,
and make it visible only for certain users.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
tracktraining said:Do you know if i can control the disable of F11 key via code?
Example: if username is equal to admin, then allow for F11 key to be
enabled else disable F11.
If i disable F11 all together then even the admin can't have access to the
tables, queries, forms, and reports .... which would cause a lot of
problems
for future updates.
Thanks,
Tracktraining
--
Learning
Graham Mandeno said:Hi TrackTraining
The best way to hide objects from users is to hide the database window
and
disable the F11 key.
If you really want to hide individual objects but show the database
window,
then right-click on the object and choose "Properties". You will see a
"Hidden" checkbox there.
Note that the user can still show hidden objects by going to
Tools>Options.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Hi All,
can queries be hidden from the end users?
Thanks,
Tracktraining
tracktraining said:Hi Graham,
you said that it is possible to show the database window using code....
can
you tell me how? anything would be much appreciated.
Thanks.
--
Learning
Graham Mandeno said:Unfortunately the database properties that control startup options do not
take effect until the next time the database is opened.
I would suggest the version of your database you release for production
should be different from the one you are developing. When you are ready
to
release a new version, copy the development database (or even better,
make
an MDE) and set the startup option properties on the copy.
Of course, you can always show the database window using code. You could
have a command button on your main form that displays the database
window,
and make it visible only for certain users.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Do you know if i can control the disable of F11 key via code?
Example: if username is equal to admin, then allow for F11 key to be
enabled else disable F11.
If i disable F11 all together then even the admin can't have access to
the
tables, queries, forms, and reports .... which would cause a lot of
problems
for future updates.
Thanks,
Tracktraining
--
Learning
:
Hi TrackTraining
The best way to hide objects from users is to hide the database window
and
disable the F11 key.
If you really want to hide individual objects but show the database
window,
then right-click on the object and choose "Properties". You will see
a
"Hidden" checkbox there.
Note that the user can still show hidden objects by going to
Tools>Options.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Hi All,
can queries be hidden from the end users?
Thanks,
Tracktraining
Graham Mandeno said:The easiest way is to use DoCmd.SelectObject:
DoCmd.SelectObject acTable, ,True
The first argument is the page of the Db Window you want to show - use one
of the built-in constants: acTable, acQuery, acForm, etc
The second argument should not be supplied, unless you want to select a
particular object.
The third argument should be True, which means you want to select the object
in the Db Window.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
tracktraining said:Hi Graham,
you said that it is possible to show the database window using code....
can
you tell me how? anything would be much appreciated.
Thanks.
--
Learning
Graham Mandeno said:Unfortunately the database properties that control startup options do not
take effect until the next time the database is opened.
I would suggest the version of your database you release for production
should be different from the one you are developing. When you are ready
to
release a new version, copy the development database (or even better,
make
an MDE) and set the startup option properties on the copy.
Of course, you can always show the database window using code. You could
have a command button on your main form that displays the database
window,
and make it visible only for certain users.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Do you know if i can control the disable of F11 key via code?
Example: if username is equal to admin, then allow for F11 key to be
enabled else disable F11.
If i disable F11 all together then even the admin can't have access to
the
tables, queries, forms, and reports .... which would cause a lot of
problems
for future updates.
Thanks,
Tracktraining
--
Learning
:
Hi TrackTraining
The best way to hide objects from users is to hide the database window
and
disable the F11 key.
If you really want to hide individual objects but show the database
window,
then right-click on the object and choose "Properties". You will see
a
"Hidden" checkbox there.
Note that the user can still show hidden objects by going to
Tools>Options.
--
Good Luck
Graham Mandeno [Access MVP]
Auckland, New Zealand
message
Hi All,
can queries be hidden from the end users?
Thanks,
Tracktraining