first of all, if i use the Data Sources (ODBC) administrative tool to set up
a User DSN, one of the type/driver options is 'Microsoft Access Driver'.
i'm pretty sure that's the option i want to use! however, when i start the
DTS wizard, 'Microsoft Access Driver' (at least the English version!) is NOT
available! The only English option is 'Microsoft Access', which lets me
pick an access .mdb file. But if i try it this way, once i pick the file,
the import fails anyway with error: "Cannot start your application. The
workgroup information file is missing or opened exclusively by another
user." i don't know what file this refers to - any ideas?

i tried using the Spanish and German versions of 'Microsoft Access Driver',
which do exist, but the UserDSNs list doesn't list my DSNs!

since i can't workaround by using the Spanish or German options listed, how
can i take them off the list? i'd rather not see the clutter.

Hosed here ... something might be wrong with the .mdb too, though cuz access
crashes when i try to export tables to txt/csv. forced to export these to
excel as an intermediary format for now & it sux.

any help would be much appreciated! THANKS! =)

In the DTS designer there is an Access icon to use. Can you use that ?

You are probably missing the security database

How can I dynamically set the Access System Database
(http://www.sqldts.com/default.aspx?241)

1)While creating the DTS package with DTS Import/Export Wizard, choose the
source as Microsoft Access ,choose the file path of the .mdb file, provide
the user name and password.
2) Click on the advanced properties for the provider in the dialogue box
and for the value Jet OLE DB:System Database, please enter the path to the
system.mdw file
for Jet OleDBatabase Password, please enter the admin password for the
access DB
3) Now the transfer should complete succesfully.

In case the transfer of data still fails , then things to be checked would
be
1)If the file path where the access mdb files are shared has the
appropriate share permissions
2)system.mdw file path is correct and it is the correct system.mdw file
associated with the database.


--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"=Snappy=" <no!> wrote

Thanks very much, Allan! =)

The missing system.mdw was the problem! Once i pointed to that, i got it to
work.

FYI once i entered the 'advanced' tab and specified my admin pw, i had to
blank the 'user name' & 'pw' boxes on the regular (non-advanced) wizard
page.

"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote