|
George, I forgot to answer your question on security. Here are my thoughts. I would set up a system DSN administered by the MIS department and make it read-only. This should prevent anyone from writing to the file. Users would then point to the system DSN and not to a user defined DSN. Also, when teaching users Access, never show them how to set indexes on their links. As long as you don't specify the key files, a user can not write to the file. If you are writing applications in Access, it is relatively simple to create user accounts within Access itself and lock down the database to authorized users. Keep in mind, however, that a smart user can always get around most security precautions. The only way around this is to not install the ODBC drivers on their machines if you don't trust them. --Paul Holstein iWork Software, L.L.C. On Fri, 5 May 2000 00:11:09 -0600, BPCS-L@midrange.com wrote: > Paul, > > Thanks for the feedback. Maybe you can help me lick this one. The issue I'm > getting is when I join multiple large tables. The error I get isn't a > timeout. I can't remember the exact verbiage, but it implied that it > forecasted how long the query would take, and the forecast exceeded some > threshold. The message was returned immediately after submitting the > request. I get the same message in green screen SQL command line on the 400 > sometimes. It happens when I do a monster query against the > GHH==>GLH==>GCR==>GSV. Pass throughs in this situation get the same > response. > > Oracle and Informix seem to be able to recognize that most of the records > are being filtered out of the primary and apply the filter to the parent > table before joining to the children. The 400 seems to do all the joins > first then filter on the conditions last. Am I writing the queries wrong? > > While we're on the subject of pass-through queries, do you know of a way to > pass a where condition into the pass-through query like you do with a > regular one by putting your prompt text into square brackets on the criteria > line? I know you can do it in VBA, but I'm wondering if there's something > I'm missing in the query builder. > > Also on your point about MS Abcess being robust and user friendly--I agree, > but am scared to show users too much because of the damage they can do with > update queries. I'm afraid of what the sysadmin would say if he saw the big > hole we blow in security too. Any ideas on how to secure the ODBC service to > limited users? > > Geo. > (801) 360-6360 > > +--- > | This is the BPCS Users Mailing List! > | To submit a new message, send your mail to BPCS-L@midrange.com. > | To subscribe to this list send email to BPCS-L-SUB@midrange.com. > | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. > | Questions should be directed to the list owner: dasmussen@aol.com > +--- _______________________________________________________ Get 100% FREE Internet Access powered by Excite Visit http://freelane.excite.com/freeisp +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.