×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
As to locking down the database, well,
1. What a given installation censors from lists and reports isn't
necessarily the same as what they keep users from accessing as
individual records. One could be more restrictive than the other, but
there's no telling which one. And even within single-record and
multi-record access, it could vary from one context to another.
2. Locking it down would also necessitate owner authority for any
triggers or periodic updates that propagate data into the database from
another application.
3. Users can access the database right now, outside of the application,
using SQL, or a HLL program, or a utility like QuestView. If they want
us to lock it down against illicit access, we certainly can (with lots
and lots of owner authority), but so far, there's been no demand for
that level of lock-down.
--
JHHL
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.
midrange.com
