Francisco H Tapia
my.lists at verizon.net
Wed Mar 12 09:56:13 CST 2003
:O ad-hoc against a SQL Server?!?!? :O I don't recommend you allowing your users save a VIEW on your server, they can seriously mis-write one and cause serious performance problems on your server. Instead if ad-hoc is really something you're looking into, why not give them an MDB w/ Read-only snapshot views access so they can build their personal queries there. If you want to keep the entire system in the ADP then I recommend that you take a look at QBF (Queries by Form) and saving the settings to a .dat or .ini of some sort, this is the road we're going to take for our system. -Francisco http://rcm.netfirms.com On Wednesday, March 12, 2003 7:37 AM [GMT-8], Susan Zeller <szeller at cce.umn.edu> wrote: : I am building an application as an ADP (Access 2002) and the : application will be completely locked down to the users. They'll : enter using an Application Role. : : I also want users to be able to do their own ad-hoc querying and : reporting off of the data in the database. I plan to give them a : separate ADP file that connects to the SQL Server database. I tried : giving them Data Writer permissions but that apparently is not enough : to save a view. I don't want to make them dbo's. I just want them : to be able to create select views on the data. How do I set up : permissions for this?