Guest login permissions

[Robert M (Bob) Bartis]

I have been working to configure MS Access 2000 as a front-end to an application running
MySQL 4.0.20-standard. Our thinking was to have a guest login with minimal privileges
(Select only) setup as the default on each users PC. This would allow anyone on the team
to access the DB using the front-end (Read-only). We also present a login screen for
those "power users". Allowing them to login and make changes to the data.

The login screen is really to confirm that the user name/password provided is recognized
by MySQL (Open/Close connection). From that point forward any operation that results in
an update would be done by opening a connection using the userid/password provided and
execute the command based on this users privileges.

I have shown that if I set the ODBC connection using my ID/password and then login as
myself using the front-end everything works as expected. I have also verified that if I
login is as guest everything works as expected. The problem comes when I set the ODBC
connection up as guest. I use the Test Data Source button to confirm I've provided a
valid Guest/password. I then login into the front end as myself or guest and click on a
button that results in a small query being run. Instead or the expected results I receive
an error that guest@stripped access denied with password YES.

This is followed by the ODBC connector screen being presented at which point if I click
the Test Data Source button the test fails, unlike the first time.  The permissions for
guest are set up as %.lucent.com and with Select privileges.

Any idea on what I am doing wrong and or if the approach taken is problematic? Should I be
following a different method?

I've attached the trace log of from the ODBC connector in which I first tested the data
source using guest as a login, then connected via the MS Access front end logged in as
guest, which succeeded and then attempted to run a small query. Saw the access denied
message and again attempted to test the data source using the ODBC connector screen which
failed this time.  Not sure where the Admin login request in the trace is coming from. I
checked my code and nowhere do I attempt a login in as Admin??? 
 <<SQL.LOG>> 
Robert M. Bartis
Lucent Technologies, Inc
Tel: [phone]
Mail: <bartis@stripped>
Pgr: <rmbartis@stripped>