Use the Upsize wizard.
Expect to have to fix some things manually after that. MDB and ADP are
very similar, but not the same. To get the best performance the amount
of work is considerable.

-Tom.

Keep in mind that might be better to keep your application as a mdb, and NOT
convert to an MS access project.

I would actually suggest that you stay with your mdb, and use linked tables
to SQL server. This approach means that you'll not have to rewrite most of
your recordset code, and in fact about 99% of what you have should function
as before. If you convert to an access project, you'll likely have to do a
fair amount of code rewriting in any case where you used DAO code.

The other advantage of this approach is that ADP's tend to be tied to a
specific version of SQL server, and using linked tables means you have no
such restrictions at all. In your case are using a fairly old version of MS
access, and you'll likely find that things will work better with linked
tables. in fact I doubt that the table design tools in access 2000 will work
with SQL server 2000 anyway, so you're not going to get a lot of advantages
by using a ADP here.