David Straker said:
Siegfried,
I can't find any way of retrieving Access-specific column properties (like
the control associated with the Access column) in ADO.NET. It may be
possible but I can't see it. I can infer one in code, from data type,
foreign keys, etc. in ADO.NET but that's pretty laborious. Sorry I couldn't
help, dude.
Will somebody from Microsoft please step in and give the facts to Scott M.
on support for DAO. He's posting the same statements about it not being
supported for 5 years in at least one other forum. I know that the big move
is towards ADO.NET but DAO is in Windows XP which is the most recent version
of Access, Access XP is supported by Microsoft therefore DAO is supported by
Microsoft. Isn't that "Logic 101"?
David, try to understand what I'm saying:
There is a difference between providing a technology for backwards
compatibilty and supporting it. MS has not supported DAO in years. By
support, I mean respond to technical inquiries about it or build new
applications using it. I don't mean include it in a product that always had
it.
If you were to call MS and ask them for support with some aspect of DAO,
they would tell you that they no longer support technical inquiries on DAO
and point you to some MSDN article perhaps.
Above you write: "Windows XP which is the most recent version of Access...".
Umm, no. WindowsXP is the most recent version of Windows (home use).
AccessXP is not a part of Windows, nor does it come with WindowsXP.
You wrote: "Access XP is supported by Microsoft therefore DAO is supported
by Microsoft. Isn't that "Logic 101"?"
Umm, no. AccessXP may allow you to use DAO (I actually don't think it will,
but haven't tried it), but it's native data technology is ADO (as it was as
well in Access 2000).
My entire point Dave is that DAO is the road backwards, you can still walk
it if you like, but MS has had a new road in place for many years now (ADO)
and they even have a newer one (2 years+ already) ADO.NET.
You misunderstand "support" for "can use".