No Projects in Access 2007

[Mary Fetsch]

I understand that Access 2007 doesn't support projects. We have currently
have several projects using Access 2000. What is suggested instead? If
someone could point me to some articles suggesting alternatives, I would
greatly appreciate it.

 

[Norman Yuan]

Yes, Access2007 STILL supports Access Project (*.ADP/*.ADE), and could well
be the last version that supports it (as rumor has it).

It is a bit difficult to start ADP in Access2007 (MS's way to disencourage
you to use ADP, I guess):

1. Click "Access" button (the round buttom at upper-left corner);
2. Click "New...";
3. Click folder icon next to "File Name" text box;
4. In "New Database" save dialog box, choose "MS Access Project" in "Save As
Type:" gropdown list.
5. Enter file name and click "OK".
6. Now, "Connecting to SQL Server: wizard starts for you to choose to either
connect to existing database or create a new SQL Server database.

Although you use Access2007, its ADP file format is still Access2003 format
(another sign MS would drop ADP). I'v heard some known bugd from previous
versions left without being fixed, some new bugs were introduced due to the
integration to SQL Server2005. So, if you only need to work with SQL
Server2000, you may want to use Access2002/2003.

Considering APD's dim future (at least for now), I'd not do anything with
existing, working ADP applications (if it is not broken, don't fix it,
right?) and look into other solution if the business needs. However, if
there only minor fixes/enhancements are needed and it is
technicalyy/economically doable, there is nothing wrong to go ahead, just
keep it in mind that next version of Access may not support it anymore.

 

[Mary Fetsch]

Thanks for your response. We really want to move forward into Access 2007
and beyond, so it looks like we'll need to do away with our projects. I'm
sure we're not the only ones facing this dilemma. What are the recommended
alternatives for us project users?

 

[Sylvain Lafontaine]

It's highly unlikely that the next version(s) of Access will drop support
for ADP because there is too many big companies using it at this moment.
What you could see - and it's pure speculation from my side - would be the
integration of the ADP functionality directly into the ACCDB format because,
when you take a look at it, there is no direct conflict or difference
between the two actual formats MDB and ADP: all forms and controls are the
same and the MDB file format already offert support for both DAO and ADO
recordsets as record source as well as support for passthrough queries and,
of course, ACCDB is only an upgrade to the MDB format.

The alternatives would be to go with ODBC linked tables (in my opinion, a
living fossil from the past) or with the .NET framework (clearly the way of
the future; however, VS.NET cannot still be seen as a RAD tool but with VS
2008, the gap has begun to close a little).

 

[Mary Fetsch]

Thanks for your response and your insight!

It's highly unlikely that the next version(s) of Access will drop support
for ADP because there is too many big companies using it at this moment.
What you could see - and it's pure speculation from my side - would be the
integration of the ADP functionality directly into the ACCDB format because,
when you take a look at it, there is no direct conflict or difference
between the two actual formats MDB and ADP: all forms and controls are the
same and the MDB file format already offert support for both DAO and ADO
recordsets as record source as well as support for passthrough queries and,
of course, ACCDB is only an upgrade to the MDB format.

The alternatives would be to go with ODBC linked tables (in my opinion, a
living fossil from the past) or with the .NET framework (clearly the way of
the future; however, VS.NET cannot still be seen as a RAD tool but with VS
2008, the gap has begun to close a little).