ADO 6

[aaron.kempf]

there is a DAO revival.

Those fat lazy fucktards in Redmond have set the clock back a DECADE by
going back to DAO.

I spit on anyone that uses DAO for anything.


And I for one-- am just glad that there is continuing support for a new
version of ADO.
And I hope that Microsoft continues to support this and other remnants
of VB6.

Because; as a whole; Access and a DAO revival-- and VB.net-- NEITHER
ONE OF THESE MAKE A DECENT REPLACEMENT FOR VB6 AGAINST ADO. Accesss &
DAO is buggy as hell.. I would rather get ass-raped then use DAO ever
for anything in my life. And productivity in VB.net?? ROFL; ROFL; ROFL

what an oxymoron

I for one-- am glad that Microsoft finally saw the light and agreed to
include a new version of ADO in vista.

I hope that someday Microsoft opens up the magic curtain and starts to
project 10 years in advance.

Because; I -- for one-- am frankly fucking pissed off that Microsoft
has been waffling on something like 'Data Access Libraries'

Moving back to DAO is unacceptable.
I would rather use Windows Me than go back to DAO.

DAO hasn't been included in office for 4 years; yeah it came back in
2003-- but I strongly disagree with that also.

All that did was make things harder for ADO developers.

When Microsoft starts COMMUNICATING-- TEN YEARS IN ADVANCE-- IS WHEN I
GIVE THEM PERMISSION TO STOP LICKING MY BALLS.

Changing course on Data Access Libraries FIVE TIMES IN FIVE YEARS IS
COMPLETELY FUCKING UNACCEPTABLE.


And I; for one-- am just stoked that there is an ADO revival.
I mean; there is a new version of ADO.. is there a new version of DAO
that I can use in vb6 code?

What a fucked up stupid ass marketing message these fucking retards are
delivering.

-Aaron

 

[aaron.kempf]

DAO revival?

they're going back to an old ass version of Jet for everything..
they're going to support all this new functionality to SET US BACK TEN
YEARS

the person that came up with this decision-- it has to be the same
person that decided that we're not smart enough to close our own
database connections (WHEN WE WANT TO MOFOS) and that we're not smart
enough to .movenext in our own datasets.

Fucking retards; they would have a more consistent strategy if they
pulled random GUESSES out of a hat.

-Aaron

 

[aaron.kempf]

READ THIS-- this has not been true for the PAST DECADE

http://blogs.msdn.com/access/archive/2006/07/27/680772.aspx

The primary application programming interface (API) for working with
the Microsoft Jet database engine from code is Data Access Object
(DAO). In Office Access 2007, new objects, properties, and methods will
be added to DAO to support the new features in the Access database
engine. For example, multi-valued fields created using the new Lookup
Wizard will be accessible from code as DAO recordsets.

In Office Access 2007, programmers will also have the option of
enhancing their Access applications with add-ins and smart panes based
on managed Microsoft .NET code. A primary interop assembly (PIA) for
Access, as well as one for DAO, will enable managed code running in
these add-ins and smart panes to manipulate Access user interface
objects and Access data.

 

[aaron.kempf]

jackass; you don't use the microsoft public servers
you use 'AccessMonster'

ROFL

do you even know how to spell nttp://news.microsoft.com?

and for the record; if someone came out and TOLD ME THAT IT WAS
SWEARING THAT GOT ME BLACKLISTED FROM nttp://news.microsoft.com/ then I
would no longer swear.

but I swear to fucking god; they've blocked hundreds if not thousands
of my posts that dont include swearing; I've seen it myself.

-Aaron

 

[aaron.kempf]

and lets just say I dont need your kids help to get shit done

I just want you kids to realize that the future isn't about DAO
and I for one; am stoked that there is an ADO revival.

ADO.net is overkill and DAO is buggy as fucking hell.

ADO6 is going to save the world!

-Aaron

 

[aaron.kempf]

so you kids admit that there IS a new version of ADO..


and yet you all sit there and claim that DAO is makign a great
revivial?


WHAT ABOUT THE ADO REVIVAL?
WHAT ABOUT THE ADO REVIVAL?
WHAT ABOUT THE ADO REVIVAL?
WHAT ABOUT THE ADO REVIVAL?
WHAT ABOUT THE ADO REVIVAL?


I'm just so excited I think that im going to pee my pants

 

[larrylinsonjr]

Aaron

I am glad that you like ADO... I prefer ADO also.



| so you kids admit that there IS a new version of ADO..
|
|
| and yet you all sit there and claim that DAO is makign a great
| revivial?
|
|
| WHAT ABOUT THE ADO REVIVAL?
| WHAT ABOUT THE ADO REVIVAL?
| WHAT ABOUT THE ADO REVIVAL?
| WHAT ABOUT THE ADO REVIVAL?
| WHAT ABOUT THE ADO REVIVAL?
|
|
| I'm just so excited I think that im going to pee my pants
|
|
|
|

 

[aaron.kempf]

Im just stoked that there is a new version of ADO; I am glad that
Microsoft is keeping ADO around and not reverting back to that unstable
DAO crap


-Aaron

 

[punjab_tom]

thank goodness that there is a new version of ADO

-Tom

 

[Master Programmer]

Yeah or worse still that fucking ADO.NET garbage. Who the **** needs
XML when you have a database. Overhyped shite for MS clones that are
brainwashed into the "Microsoft Way".

The Grand Master
Knowledge is Everything

 

[Master Programmer]

Are you stuck in a fucking time warp ??? DAO is total fucking shit, it
hasnt been around for years.

The Grand Master

 

[Ralph]

Are you stuck in a fucking time warp ??? DAO is total fucking shit, it
hasnt been around for years.

The Grand Master

<snipped>

LOL!

Hopefully, to avoid embarrassment, you don't express those comments around
grownups. There are only a couple of million 'professional' programmers that
would be very amazed to hear that DAO isn't around.

<g>
-ralph

 

[aaron.kempf]

I _TOTALLY_ agree with you on that bro.. ADO.net is BLOATWARE

who the **** needs XML when you've got a database.. shit i'll be
chuckling abuot that for days; and i totally agree with you

-Aaron

 

[Master Programmer]

Oh its still around, of course. Just no-one is so fucking stupid that
they would use it (well almost no-one).

The Grand Master
Knowledge is Everything

 

[aaron.kempf]

Ralph

I sure dis-agree.

DAO is DEAD you fucking retards

-Aaron

 

[aaron.kempf]

I mean seriously here

DAO has been DEAD for TEN YEARS

they just came out with a new version of ADO.. it is called 'ADO 6'

did they even come out with a new version of DAO (for VB6?)

ROFL

-Aaron

 

[punjab_tom]

sorry the 'Microsoft Way' changes every 18 months with ZERO DISCLOSURE
and ZERO LOGIC.

-Tom
Punjab, India

 

[dbahooker]

you guys aren't professional programmers

any that 'uses office for development' is considered even less than a
Junior Programmer than Microsoft labels even the VB.net programmers.

So yeah.. you can take your million plus sub-junior programmers and
shove them up your ass; MDB and DAO are obsolete

-Aaron
ADP Nationalist

 

[Homer J Simpson]

you guys aren't professional programmers

any that 'uses office for development' is considered even less than a
Junior Programmer than Microsoft labels even the VB.net programmers.

So yeah.. you can take your million plus sub-junior programmers and
shove them up your ass; MDB and DAO are obsolete

-Aaron
ADP Nationalist

Well, sir, you aren't a professional anything. Any competent programmer uses
the best tool for the application instead of one fits all. MS Office may
very well be the best tool for some purposes, as I have shown by using it to
replace horrendous and unworkable code written by others.

"If you only have a hammer, everything looks like a nail".

 

[dbahooker]

you're the fucking retard that is stuck in MDB land

you're the one with a single hammer and everything looks like a nail

I don't need to be a programmer. I coast on my database skills ROFL

no but seriously; MDB is crap. VB.net is CRAP. VB 2005 is too slow and
too unstable for real world use.

MIcrosoft has never made it practical to deploy the .NET framework.
I mean seriously here.. how do you tell what version of the framework
is on machine X?

please; im dead friggin serious-- tell me how to tell what version of
the framework is installed; and I'll give up ok?

(this is a trick; there is no simple standard way to do this that is
consistent through Windows 2000, XP, 2003 and Vista-- it just somehow
escaped Microsoft to give us a simple answer like this)

-Aaron