Wortz, Charles
CWortz at tea.state.tx.us
Wed Mar 12 10:42:34 CST 2003
Susan, I think Francisco's suggestion is appropriate for your situation. I have a similar situation where there is one secured FE that links to the SQL Server db for those that need to update the data. And another secured FE that downloads a snapshot of the data into a secured MDB for those that only need to read, query and report on the data. Charles Wortz Software Development Division Texas Education Agency 1701 N. Congress Ave Austin, TX 78701-1494 512-463-9493 CWortz at tea.state.tx.us -----Original Message----- From: Susan Zeller [mailto:szeller at cce.umn.edu] Sent: Wednesday 2003 Mar 12 10:22 To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer]Creating views from an adp -- permissions Hmmm.... I'm confused by both Susan's and Francisco's comments. The application I'm building is a student tracking database. The users are constently needing to do different administrative things with students like send out a letter to some subset of students about X or create a list of students for Y. They are good Access users and know how to to write queries and create reports. I don't want them to have to come to me every time they need to send out a letter and I don't want to invest a lot of time in developing a front end tool for this when they are capable of doing it themselves. I hear the concern about them writing bad queries and bogging down the database and I hadn't thought of that. --Susan -----Original Message----- From: Susan Harkins [mailto:harkins at iglou.com] Sent: Wednesday, March 12, 2003 10:01 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer]Creating views from an adp -- permissions Are you just wanting to save their preferences? I realize this is SQL Server, but Doris and I just put together an article on this for Access. The form itself offers all the "options" and the necessary SQL code that puts them together, and the user can save those settings if they want -- the code behind the form uses the FileSystemObject and a TextStream -- couldn't be simplier. I don't know whether this could be adapted or not. Susan H. ----- Original Message ----- From: "Francisco H Tapia" <my.lists at verizon.net> To: <dba-sqlserver at databaseadvisors.com> Sent: Wednesday, March 12, 2003 10:56 AM Subject: Re: [dba-SQLServer]Creating views from an adp -- permissions > :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