Mining Access 2003

I created a AS 2005 data source to an Access 2003 database on my PC. The connection tests fine, I can browse the data from AS 2005. But when I try to process the mining model, I get a userid & password error. There is no password on the Access database. When I set up the data source, the wizard wanted a userid and password - the default was Admin - and I left the password blank. The connection tested ok. I tried changing the Impersonation settings, but that gives me a deployment error. Any ideas why the model process can't find a connection?

Is the AS Client and Server on the same machine? Since the access connection string contains a path to the file, the path has to be the same from the client tools as it is from the server.

|||I assumed that it was since I was able to get a connection and explore the data from AS. I have an entry under SQL Server Management Studio that's on my machine. Let me check a few things....|||Nope, still doesn't work. It still wants a userid and password for the Access table. It doesn't like the Impersonation type if I tell it to use the current user credentials. It doesn't like the Class if a pick Default or Service Account. I even tried putting a password on the Access database - and it still says it's invalid. What really confuses me is that I can right-click the table in the data source view and explore the data in the Access database with no problem.|||Is the server physically located on the same machine as the client?|||I think that may be the problem. I've been trying to find a machine that I know has the server on it to verify the solution. But our techs are upgrading the dev servers this week. At this point, I think I'll wait until things settle down and I can upgrade my PC to the new release - then I can make sure the server gets loaded as well.

Thanks!|||

If your server's not on the same system, the reason you are seeing this behavior is that the access connection string contains a path that is relative to the location from where the connection originates. For example "C:\MyDB.mdb" on your client machine is not the same as "C:\MyDB.mdb" on the server machine.

What you can do is put the Access file on a share that is accessible via the same path from the client and the server, e.g. "\\MyMachine\MyShare\MyDB.mdb"