Talk:Microsoft Data Access Components

Microsoft Data Access Components received a peer review by Wikipedia editors, which is now archived. It may contain ideas you can use to improve this article.

Links:

Google search for MDAC +security +bulletin site:microsoft.com
MDAC release history
MDAC search on MS site
MS MDAC article
The end of the MDAC Redistributable (Brad Rhodes)
Getting started with SQL Native Client (Chris Lee)
MDAC Net-Lib change (infoWorld) - basically burnt some developers!

Short note of thanks to Microsoft developer Angel Saenz-Badillos

I asked for comment on this article, and he kindly pointed me to two interesting articles. Many thanks for this assistance! - Ta bu shi da yu 02:45, 11 August 2005 (UTC)[reply]

Connection pooling

We need some info about this. See Pooling in the Microsoft Data Access Components. - Ta bu shi da yu 03:34, 28 November 2005 (UTC)[reply]

Feedback

See here :-) I'm pretty happy with the feedback! Woohoo! - Ta bu shi da yu 04:23, 29 January 2006 (UTC)[reply]

Page move

I've moved the Microsoft technology variation of this four letter acronym to its full name, Microsoft Data Access Components. While in the scope of computing, MDAC may be a popular acronym, but the full name is certainly a more correct name for the article than its abbreviation, especially in light of there being other uses of the acronym. Warrens 23:51, 24 March 2006 (UTC)[reply]

In doing so, you did several things.

You have removed the page history. I wrote most of this article, and it was all in the page history. I have been forced to do a page merge to get the history back. There are very few advantages to editing Wikipedia: one, however, is that people can see what you wrote. If you remove my page history, you do a disservice to me, and you reduce the incentive to edit the site.
~~This article had a talk page. Where is it now?~~ - fixed - Ta bu shi da yu 15:49, 3 August 2006 (UTC)[reply]
It is most commonly known as MDAC, not Microsoft Data Access Components, so this is wrong. We use the most commonly used name.

I realise that you meant well, but please be more careful in future! - Ta bu shi da yu 15:34, 3 August 2006 (UTC)[reply]

Windows Data Access Components 6.0 - Windows Vista

I would like to have a seperate section for Windows Data Access Components 6.0, as will be included with Windows Vista: Windows Data Access Components SDK

I also would like to have the MDAC 9.0 beta out of the MDAC Release list, since it was never an official release. MDAC 9.0 is replaced by SQL Native CLient.

Thank you.

--KlaasNekeman 12:00, 24 October 2006 (UTC)[reply]

No probs... however, if you would like you can click on the edit button and type in some info yourself :-) - Ta bu shi da yu 08:38, 12 December 2006 (UTC)[reply]

Done - thanks for pointing this out! - Ta bu shi da yu 08:51, 12 December 2006 (UTC)[reply]

Microsoft Jet Database Engine and JRO

"In later versions of Jet, the engine was extended to run SQL queries,"

That's wrong. Jet could always run SQL Queries. But more to the point, the only versions ever included in MDAC could always run SQL Queries.

"a database engine used for Microsoft Access, Microsoft Exchange Server"

The database engine used by exchange is a different database engine than that used by Access. They are both Jet engines, but they are different Jet engines. The Exchange engine does not run SQL queries, does not include Rushmore technology, and was not ever included in MDAC.

"a modified form of an Indexed Sequential Access Method (ISAM) database"

I think this is wrong, although it is a common myth. I think that Jet uses the Random Access database primitives provided by the operating system, not the Sequential Access database primitives. The confusion arises because the Access and then DAO also provided a Sequential Access API, which was intended to be attractive to dBase programmers, but which was ananthama to RDMS programmers. dBase and dBase like programes originally use ISAM, hence the Installable ISAM interface for accessing dBase files. You will find insults claiming that Access is an ISAM system, but I don't think you will be able to find anything authorative supporting the assertion that the Jet Engine is ISAM. Since I never never met anyone who used Access 1.0, which apparently was only a pale prelude to Access 1.1, Access 2.0, and Jet 2.5, I'm unable to say if it was an ISAM system, but it wasn't called Jet, and certainly wasn't included in anything called MDAC.

And finally, a general problem with the use of the past tense. "DAO allowed programmers access to the Jet engine."

You've got a problem with the tenses, because although DAO is no longer part of MDAC, it is still part of Windows (at least until Vista), and still part of Access.

I don't have a solution to the problem, because it appears that merely changing everything to the present tense would be even worse.

Also, it appears that MDAC, ADO, OLEDB and ODBC are obsolete and depreciated technologies, so perhaps that whole classification needs to be rethought

(david)218.214.18.240 11:01, 29 December 2006 (UTC)[reply]