Encountering a bit of a head-scratcher:
I've got a VFP application that uses a database in SQL Server. This application resides on a shared fileserver (same server on which SQL Server resides).
* User A has no problem
* User B gets error indicating problem with opening a table.
* Both user A and B are member of Active Directory X
* Active Directory group X is registered into SQL Server and assigned db_datareader, db_datawriter and db_owner roles on the database.
* The application normally uses a DSn to define connection parameters.
* A System DSN has been configured to establish connection to the database, when testing connection it works for both user A and user B

As part of the troubleshooting, I've added a bit of code at the program startup that does the following:
* Open a connection to SQL Server using SQLSTRINGCONNECT() with connection parameters that are identical to what was configured within the System DSN
* After confirming the handle returned by SQLSTRINGCONNECT() is a neither negative nor zero, it issues a SQLEXEC() that queries contents of a table that should be in the database.
* modal messagebox is used to display result of the above.
* closes the connection.

From this troubleshooting code, the behavior indicates that:
* When user A is logged on using own workstation, there is no problem.
* When user B is logged on using own workstation the connection is succeeding (handle returned is non-zero positive value) but the query fails as if table is not accessible (i.e. error message says table does not exist)
* When user A is logged on using user B's workstation there is no problem -- program works fine
* When user B is logged on using user A's workstation there is no problem -- program works fine

Have tried registering user B into SQL Server and assigned roles of db_datareader, db_datawriter and db_owner for the database -- no change in results.

Have restarted the server and workstations in question -- no change in results.

Does anybody have any thoughts on what's going on and offer suggestions?