On 24 Aug, 18:52, "BruceM" wrote:
If they've used their own credentials via your mdw (i.e. utilizing
your security mesures rather than circuventing them) to connect to the
data in the BE from within Excel then in my book that is legitimate
usage and IMO should be accommodated.

Is there documentation that what you describe is possible?


You serious? Try these KB articles:

ACC97: How to Use IDC Files to Query a Secure Microsoft Access
Database
http://support.microsoft.com/kb/161172

How to open a secured Access database in ADO through OLE DB
http://support.microsoft.com/kb/191754

How To Open an Access Database with User Security [using DAO]
http://support.microsoft.com/kb/163002

How to open a secured Microsoft Access database in Visual C++
http://support.microsoft.com/kb/270663

HOW TO: Connect to a Security-Enhanced Microsoft Access Database by
Using Microsoft Visual Studio .NET
http://support.microsoft.com/kb/823927

How To Use ADO to Refresh/Create Linked Table for Password Secured Jet
4.0 Database
http://support.microsoft.com/kb/240222

etc etc

Try these simple steps: Open Excel 2003. On the menu, choose: Data,
Import External Data, New Database Query. In the resulting 'Choose
Data Source' dialog, select New Data Source, and click OK. In the
resulting, 'Create New Data Source' dialog, step 1: enter a name (for
the DSN), step 2: choose Microsoft Access Driver, step 3: click the
'Connect' button. In the resulting 'ODBC Microsoft Access Setup'
dialog, choose you mdb 'Database' (I recommend you use a copy here),
choose your mdw 'System Database', click the 'Advanced' button and
enter a valid username and password combination. OK to each dialog to
get you back to the 'Choose Data Source' dialog, select the newly-
created DSN and hit OK to take you to the main MSQuery dialog (cancel
the 'Add tables' dialog if it shows on start up). Hit the SQL button,
type in a Jet syntax SQL statement (e.g. CREATE VIEW DropMe AS SELECT
1, click the OK button, continue past the odd 'query cannot be
displayed graphically' message and the SQL will be executed.

Jamie.

--