How to convert mdb -> adp ?

[Tomasz J]

Hi,

Stupid question, but after some googling I still cannot find the answer.
How do I convert regular Access 2000 file (.mdb) to Access Project 2000
(.adp)?
I am talking about queries, forms, reports, modules conversion only - the
front-end part.
I know how to migrate the data to SQL Server - this has been handled.
One constraint: I cannot migrate to any newer version like Access 2007 - it
must stay ver 2000 (many users, license purchasing issues).

Thank for any pointers,

Thomas

 

[Tom van Stiphout]

On Thu, 24 Apr 2008 14:36:49 +0200, "Tomasz J" <[email protected]>
wrote:

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.

 

[Tomasz J]

Ach, I knew I was a stupid question. I did not know the second option
"Create new database" had to be selected. I have already migrated the data
using "Microsoft SQL Server Migration Assistant 2005 for Access" and went
half way through countless post changes.

Thanks,

 

[Albert D. Kallal]

Hi,

Stupid question, but after some googling I still cannot find the answer.
How do I convert regular Access 2000 file (.mdb) to Access Project 2000
(.adp)?
I am talking about queries, forms, reports, modules conversion only - the
front-end part.
I know how to migrate the data to SQL Server - this has been handled.
One constraint: I cannot migrate to any newer version like Access 2007 -
it must stay ver 2000 (many users, license purchasing issues).

Thank for any pointers,

Thomas

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.

 

[a a r o n . k e m p f]

I would suggest that you don't listen to these people.

SQL Server has a great future-- Access / JET / DAO is going away.

ADP are not tied to a specific version of SQL Server.
ADP are not going away.

The Table Design tools _DO_ work with SQL 2000.
Where do you come up with this stuff?

Yes, there are some 'quirks'-- with SQL 2005.. but nothing that is
that big of a deal.

Nice try-

-Aaron

 

[Tony Toews [MVP]]

SQL Server has a great future-- Access / JET / DAO is going away.

Access, Jet and DAO are still present and still in use.

ADP are not going away.

However there were no enhancements made to ADPs in A2007.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[a a r o n . k e m p f]

Tony;

where do you come up with this campaign of mis-information?

ADP has gotten plenty of enhancements-- with every version-- while JET
has been left to ROT.
JET still doesn't work over WiFi or VPN or WAN.

-Aaron