Application Info:

- Access Project 2002 FE
- SQL Server 2000 BE
- MDAC 2.8 SP1 on Win XP SP2
- User base: 1400+

The application is a survey. So far, 396 people have connected successfully and 4 have reported the issue described below.

Problem:

A user can't connect to the DB on his machine (logged on as him) but can connect if he logs on to my machine (as him).

We all logon to a domain so I can't figure out if there's a component like MDAC (our versions are the same) that's outdated on his machine or if he doesn't have permission to something.

It seems like it would be component related since he would have less permission on my machine given that he's never logged on to it before and all rights would be granted from the domain.

If I "SHIFT" into the Access .adp I can't see tables or queries on his machine but when I go to File | Connection and use the Test Connection button I receive the "Test connection succeeded." message.

Does anybody know what else Access and/or SQL Server cares about on the local machine that would be causing the failure?

Thanks,

Chris Davis