Need to understand Microsoft Jet Engine

[Fred48]

Hi,

We have a product written in VB 2005 that uses Acesss DB to store date from mainframe processing. Currently we are using the Jel.OLEDB 4.0 with engine type 5which are Access 2000, I believe. Our concern is drop support for this particular Jet Engine.

The question is do we need to upgrade the Jet Engine to a current release Access 2007 (with extension of .accdb) or can we stay at the current Jet Engine.

Also, if we upgrade do we need to ship only the new Jet Engine?

Thanks

 

[Sorwen]

First let me say these observations are from using Access 2003/2007 and not some Microsoft quru to be 100% sure of the ins and outs. That said 2007 uses Ace not Jet so you can see the problems are right from the start. The next problem is who/how you are going to deploy this too. Keep in mind that if anyone needs to access the database directly they must either be running Access 2007 or be one of the few people that actually has bothered to install the importer for 2003 because it cannot natively read Access 2007 files. And the list goes on and on and on.

My company has not fully converted to 2007 and it has been a nightmare because I had to redevelop all of my tools to be able to work with both platforms. I'm not allowed to force install of Jet. If you are going to have it install Jet rather than assume the user will have it then I say for now stick with 2000 Access format for a wider compatibility and far fewer possible headaches.

-I hate Microsoft!
-Forever and always forward.
-My kingdom for a edit button!