application migration

[pnutjell-googlegroup]

Hi all,

I wrote a VB3/Access 2.0 app way back in '94. User would like to
upgrade such that the application no longer relies on outdated
software.

The application is: single user..... very simple database, just a
couple of tables..... lots of old DAO code.. compatibility layer... a
few VBX's.

Goal is to migrate such that same app functionality is available.

I'm proposing, in this order:
1. Access front end, JET backend, DAO.
Pro: faster developement
Con: rumors of DAO's demise

2. Access front end, SQL Express, ADO
Pro: no longer have to worrry about rumors of DAO's demise
Con: ADO's rumors of demise

3. VB.Net front end, SQL Express backend, ADO.Net.
Pro: Many healthy years ahead for these tools
Con: steeper learning curve, slower dev

Thoughts? Thank you....

 

[Allen Browne]

DAO is not about to "demise." The Microsoft Access team now have their own
version of JET, with a matching AceDAO. That's clearly the future of Access.
You can research more of this at the Dev. team's blog:
http://blogs.msdn.com/access/

ADO has already "demised." It is replaced with the very different ADO.NET.

There is absolutely *no* way that it is worth the effort of developing a new
..NET application for this single user, simple database that is already built
and proven in Access. It's usually a simple task to replace the
compatibility layer, so the only significant task might be replacing the
VBXs.

 

[pnutjell-googlegroup]

Thanks Allen, so the backend we'll keep as Access, just move it on up
to 2003 format MDB.

However....
The front end is in VB 3, the backend is Access 2.0; front end has DAO
2.x logic in it. There are currently no Access forms/reports.

We're moving off the VB front end to a re-write into either Access
front end or VB.Net. So there's substantial stuff to be done in terms
of all that old DAO 2.x logic.

I would say that Access can easily do the job for the front end.

So that leaves the question of DAO - we'd use DA0 4.x, and do you see
any need to be worried about its longevity or need for conversion over
the next few years? I think you're saying not to worry....

Thank you,

Steve

 

[Allen Browne]

The new database engine in Access 2007 (called ACE) is DAO-based. DAO is the
future, at least in the Access world. My preference will continue to be DAO
for developing in all versions of Access, including 2007.

Right, if the front end was VB3, there will be some re-writing to do in
Access.