J
John Hackert
In my ongoing development of a SQL Server back-end / Access adp front-
end migration from and mdb, I'm encountering an issue I cannot
understand that seems to relate to permissions under the adp.
The system configuration includes a test server running SBS 2003 R2
and two test clients running Win XP SP2.
SQL Server Express 2005 SP2 is installed and working on all machines,
and connectivity is established and stable across the test system for
test users: user logons to windows SBS are successful, and on the
clients in SSMSE all database elements are visible, including the
specific ability to test-execute a stored procedure on the client and
retrieve the expected recordset - including under a test-user logon.
Integrated windows security is used.
Regarding the adp itself, it runs fine on a given client if the client
logon is either The Administrator, or if I change a test user's
permissions to the Administrator Template (from, eg, User Template or
Power User Template). However, when a test user is logged on (again
with seemingly working permissions in SSMSE), recordsets that are
derived from parameterized stored procedures are not populated.
In SSMSE, the test user's default schema is set to "db_owner," and the
database role membership is set to "db_owner." My attempts to adjust
test user permissions short of the administrator level have not
corrected this phenomenon. As one clue, I notice in SSMSE that on the
icon representing the SQLEXPRESS instance, the white circle remains
empty when a client is logged on, whereas the green arrowhead appears
when the Administrator is logged on.
Any insight would be much appreciated - obviously assigning users to
administrator roles is not practical.
end migration from and mdb, I'm encountering an issue I cannot
understand that seems to relate to permissions under the adp.
The system configuration includes a test server running SBS 2003 R2
and two test clients running Win XP SP2.
SQL Server Express 2005 SP2 is installed and working on all machines,
and connectivity is established and stable across the test system for
test users: user logons to windows SBS are successful, and on the
clients in SSMSE all database elements are visible, including the
specific ability to test-execute a stored procedure on the client and
retrieve the expected recordset - including under a test-user logon.
Integrated windows security is used.
Regarding the adp itself, it runs fine on a given client if the client
logon is either The Administrator, or if I change a test user's
permissions to the Administrator Template (from, eg, User Template or
Power User Template). However, when a test user is logged on (again
with seemingly working permissions in SSMSE), recordsets that are
derived from parameterized stored procedures are not populated.
In SSMSE, the test user's default schema is set to "db_owner," and the
database role membership is set to "db_owner." My attempts to adjust
test user permissions short of the administrator level have not
corrected this phenomenon. As one clue, I notice in SSMSE that on the
icon representing the SQLEXPRESS instance, the white circle remains
empty when a client is logged on, whereas the green arrowhead appears
when the Administrator is logged on.
Any insight would be much appreciated - obviously assigning users to
administrator roles is not practical.