importing Access DB ito SQL 2005 DB

Did you try 'Admin'?

yes

Have you tried leaving the user name blank but filling in the pwd? (Not sure it'll work, but it's possible...I'd also try using no user/pwd and seeing if it asks for it on processing)

-Rachel

yes and yes

Just ran a quick test - added a password to a DB then tried to export a table from it to a SQL db. It asked me for the SQL side user name and password, not the DB side, which makes sense - you need the end point's read/write access. I may be stating the obvious for you again, but have you tried using the server's login and pwd?

-Rachel

you saying i need the SQL account user credentials, doesn't make sense. the MDB is password protected, when trying to import a non-password protected MDB, it runs fine. with password protected MDB, i get prompted. I have a domani account with god privelages on the SQL server, adn using that i'm getting no where. same error as i've been recieving all along:

OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Cannot start your application. The workgroup information file is missing or opened exclusively by another user

i've googled it, lots of ppl experiencing the same problem, but can't seem to find a fix so far.

thanks for your efforts btw

sorry, and wrong error message i've sent you there - this is my err: "Cannot start your application. The workgroup information file is missing or opened exclusively by another user"

The default credentials are "admin" with a blank password. I'm not sure what you're doing, or how your doing it, but in some case you must specify the Workgroup file required for these operations even if the file is "secured" using the default system.mdw file.

Note the concept of "password protected" and "secured" are two different scenarios. You can "password protect" a database without securing it through User Level Security. If you ONLY password protect the db, then you ONLY need to enter the password - there is no username. If you use User Level Security (or if your import process requires you to specify the username/password) then you must supply both a username and password (even if the password is blank).

So - How are you doing the Import?

Genius...... if i could send kisses down over the internet i would. Thanks for your continued effort. much appreciated.

Aw, gee! (blush)

Glad I could help...and I learned something new in the process! (Of course, I'd be interested to know what benefits are gained drawing data IN to SQL vs pushing it out from Access.)
-R

long story:
-third party Access app
-i'm pulling some data from it
- using the data to populate a SharePoint web part that needs a SQL database to drive it

thanks again.