Allowing Users to Run Queries Without Showing the Database Window

[Drahala via AccessMonster.com]

I have an access front end that connects to a SQL backend, and is designed in
such a way that the users never see the database window or default access
database menu bar, only the forms and menus that I want them to see.
Specifically:

1. I have set a startup form

2. I have a personalized shortcut menu bar

3. I have disabled the bypass key

4. I have disabled all keystrokes not used by my application in the form
open event

5. I have unchecked the following option in the startup:
* Display Database Window
* Display Status Bar
* Allow Full Menus
* Allow Default Shortcut Menus
* Allow Built-in Tool Bars
* Allow ToolBar/Menu Change
* Use Access Special Keys

I want to know if it's possible to keep this configuration but allow the
users the ability to create and run adhoc access queries against back end
views, and allow them to export the results to an excel spreadsheet.

 

[Klatuu]

No. What I would suggest would be to create another database with the tables
linked and allow them to build their own queries or reports.

 

[Drahala via AccessMonster.com]

That's what I thought. The second database is plan B, but it would be much
cleaner if this function could be managed in the same front end. Thanks for
the quick response.

No. What I would suggest would be to create another database with the tables
linked and allow them to build their own queries or reports.

I have an access front end that connects to a SQL backend, and is designed in
such a way that the users never see the database window or default access

[quoted text clipped - 22 lines]

users the ability to create and run adhoc access queries against back end
views, and allow them to export the results to an excel spreadsheet.

 

[Klatuu]

It would be nice. I think we all have had this challenge before, but a
database is either secure or it isn't.
--
Dave Hargis, Microsoft Access MVP

That's what I thought. The second database is plan B, but it would be much
cleaner if this function could be managed in the same front end. Thanks for
the quick response.

No. What I would suggest would be to create another database with the tables
linked and allow them to build their own queries or reports.

I have an access front end that connects to a SQL backend, and is designed in
such a way that the users never see the database window or default access

[quoted text clipped - 22 lines]

users the ability to create and run adhoc access queries against back end
views, and allow them to export the results to an excel spreadsheet.