Access97 to XP upgrade of DAO code

[Douglas J. Steele]

DAO is still supported. In fact, if you're strictly using a Jet database,
DAO is still superior (and probably always will be) to ADO. As far as I'm
aware, Access 2003 even includes the DAO reference by default.

Sometimes code runs fine because the problem code isn't being used. When you
try to make an MDE, though, all the code gets checked. Open any code module,
and select Compile from the Debug menu. That should highlight whatever
problems there are in your database.

 

[John Gilchrist]

I understood that Microsoft was no longer going to support the Jet Engine
and DAO code in later versions of Acess.

I have an Access97 application which uses DAO code, and I was expecting big
problems when I tried to upgrade to Office XP. I converted the file from
Access97 to Accexx XP 2002, and the conversion seemed to go very cleanly. I
got one "some portions failed to compile" alarm, but I can't find the
problem - everything seems to work.

The alarm implied that I would no longer be able to compile, but I have made
code changes and the program ran OK. I did try to create an MDE database
file and was un-successful.

1. Did Microsoft change their mind - are they continuing to support DAO
with Office XP???
2. What is signifigance of my failure to make an MDE database file?

Thanks - John

 

[Douglas J. Steele]

As I implied before, the recently-released Access 2003 continues to use Jet,
and I've heard that the next version of Access (currently code-named Access
12) will as well.

 

[John Gilchrist]

Doug,
Thanks for your quick reply - I found my problem code - some event code
which I copied from one form to another, and had no matching control
references on the new form.

I was using the Jet Engine in Access97, and I assume that I still am using
Jet after conversion to 2002. Does Microsoft plan to discontinue the Jet
engine at some time in the future. I thought I read that somewhere.

Thanks again,
John

 

[david epsom dot com dot au]

Long Term,
The OS File System may integrate with SQL Server, and
..Net UDF's are expected in SQL Server. If and when
those things happen, there may be no reason to use Jet.

Short Term,
Does anyone know why Jet 4.0 is now installed as part
of the operating system ?

(david)