Are there known issues with Vista and Acc2003

On Feb 27, 11:20 pm, "David W. Fenton"
wrote:
you
took the "no longer recommended" path and stuck with DAO, even for
new projects. Isn't it reasonable for someone to take the same
approach now with ADP, ADO, etc?

No, it is not.

think about the difference between a native technology and a
translation layer

Oops, missed this earlier!

That's a valid point against ADO if you are only interested in
performance. Now think about data integrity: some database constraints
(including primary keys) cannot be implemented with indexes and
Validation Rules alone (big hint: table-level CHECK constraints). But
that that's just two issues out of many so let's not do the ADO vs DAO
thing again here and instead focus on the question in hand i.e. should
one avoid a feature (ADP) merely because 'Micosoft support' no longer
recommends it?

Jamie.

--