Can't import Access DB into MSDE

I want to move my Access 2K database into MSDE. The Access Upsizing
Wizard crashes (a known bug wi A2K), so I'm using the following
suggested method:
Access --> New --> Project (Existing Database)
This asks for the name of the .adp file to create and then launches
into the Data Link Properties dialog box (so far so good) I select my
MSDE server from the drop-down, enter the sa account & passwd, attach
a database file and try to select the .adp file that was just created.
Unfortunately, the "Select SQL Server Database File" dialog is looking
for an .MDF file, not an .ADP file.
If I try to kludge it and select the .adp file anyway, the Test
Connection produces an error:
"Test connection failed because of an error in initializing
provider. The header file "D:\test.adp" is not a valid database file
header. The FILE SIZE property is incorrect."
Any suggestions on how to proceed?
Note:
I've got Access 2000 SP1, Visual Studio.Net 2002, MSDE and SQL Web
Administrator running on XP Prof SP2.
See comment inline.
"*no spam*" <no0spam@.yahoo.com> wrote in message
news:34300eeb.0409231458.727df1ee@.posting.google.c om...
> I want to move my Access 2K database into MSDE. The Access Upsizing
> Wizard crashes (a known bug wi A2K), so I'm using the following
> suggested method:
> Access --> New --> Project (Existing Database)
You should:
Access-->New-->Project (New Database)
Here, "Database" means a database on MSDE/SQL Server. The wizard will create
a database on MSDE, so that it can transfer data in *.mdb to the newly
created database on MSDE. *.adp file doen not contain a database (as *.mdb
file does), it is a pure front ent app, containing forms, reports, code
modules. You only select "...Project(Existing Database) when you know there
is a database on MSDE that you want to transfer data from MDB to.

> This asks for the name of the .adp file to create and then launches
> into the Data Link Properties dialog box (so far so good) I select my
> MSDE server from the drop-down, enter the sa account & passwd, attach
> a database file and try to select the .adp file that was just created.
> Unfortunately, the "Select SQL Server Database File" dialog is looking
> for an .MDF file, not an .ADP file.
> If I try to kludge it and select the .adp file anyway, the Test
> Connection produces an error:
> "Test connection failed because of an error in initializing
> provider. The header file "D:\test.adp" is not a valid database file
> header. The FILE SIZE property is incorrect."
> Any suggestions on how to proceed?
> Note:
> I've got Access 2000 SP1, Visual Studio.Net 2002, MSDE and SQL Web
> Administrator running on XP Prof SP2.
|||Norman - Thanks for the suggestion. I gave it a try and ended up back
at the Access/MSDE bug. Access produces an "Overflow" error and the
database just gets created in Access
Might there be some other way to do this?
"Norman Yuan" <nobody@.nowhere.no> wrote in message news:<#CR1H5coEHA.2636@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> See comment inline.
> "*no spam*" <no0spam@.yahoo.com> wrote in message
> news:34300eeb.0409231458.727df1ee@.posting.google.c om...
> You should:
> Access-->New-->Project (New Database)
> Here, "Database" means a database on MSDE/SQL Server. The wizard will create
> a database on MSDE, so that it can transfer data in *.mdb to the newly
> created database on MSDE. *.adp file doen not contain a database (as *.mdb
> file does), it is a pure front ent app, containing forms, reports, code
> modules. You only select "...Project(Existing Database) when you know there
> is a database on MSDE that you want to transfer data from MDB to.
|||It is impossible to get MSDE/SQL Server database created in Access. It is
conceptually wrong. However, if you specified to "create a client/server
application" in the "Upsizing wizard" (*.adp) and the ADP file did get
created, then you can open the ADP file to verify whether the ADP file can
connection the MSDE or not. You do:
1. Double click the *.adp file;
2. Click "File->Connection..."
3. In "Data Link..." dialog box, select/enter MSDE Instance name, select
autnetication mode (Windows integrited, most likely), and try to find the
new database name created by Upsizing wizard in "Select the database on the
server" dropdown list. If you found it, that means the new database is
created on MSDE, if not, means the Upsizing wizard failed before the
database got created (it is not uncommon that Upsizing Wizard failed to
create database on MSDE/SQL Server, due to different reasons).
If the the database did get created, but the data from *.mdb did not get
transferred fully, then you can clear out the incomplete data in the
database in ADP project (remember, the data is not in ADP file, ADP file is
just a front end app to MSDE), verify the database has the ame structure as
the tables in MDB, and go back to the MDB file to re-run the Upsizing
Wizard. This time you choose "Use existing database" and do not need to
create another ADP file (You can create/open numerous ADP file against a
database on MSDE at any time by simply launching Access, when needed).
HTH
"*no spam*" <no0spam@.yahoo.com> wrote in message
news:34300eeb.0409232352.4d4014e0@.posting.google.c om...
> Norman - Thanks for the suggestion. I gave it a try and ended up back
> at the Access/MSDE bug. Access produces an "Overflow" error and the
> database just gets created in Access
> Might there be some other way to do this?
> "Norman Yuan" <nobody@.nowhere.no> wrote in message
news:<#CR1H5coEHA.2636@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
create[vbcol=seagreen]
*.mdb[vbcol=seagreen]
there[vbcol=seagreen]