i believe that she is biased and an MDB sissy.

LONG LIVE ADP

More importantly; i dont know if i believe that
mchip@online.microsoft.com is really a valid real microsoft address.

Additionally 'That is what the Access team is recommending these days
because it's more flexible (local storage, etc).'

This constitutes HERESAY-- she heard someone who said that their uncle
reccomends that.

I would gladly challenge anyone on the access team at Microsoft to a
good old-fashioned fist-fight

they just are too much of a wimp to learn TSQL.

TSQL is the only way-- the best language in the world.

Anyone that reccomends anything in MDB ever is obsolete and should be
waiting in line at the unemployment center.

Can you TRACE using an MDB file? (sure you can ODBC trace using windows
but mdb on mdb uses oledb right?)

Can you RUN a sproc in an MDB?

not really.

How easy is it it take a sproc with parameters and bind it to a form in
mdb? it takes about 20 lines of code and a bunch of ugly DAO crap

in ADP?  if you have a sproc that looks for a parameter named @txtPLU
it will automatically negotiate this to a control named txtPLU

i claim that anyone that still uses MDB hasn't used this functionality
in ADP; because this is the only reason that anyone would use mdb--
because they dont understand how to bind sprocs to forms and reports.

Sure, microsoft has done a crappy crappy job of showing that feature to
people.
Is that my fault?

Is it my fault that MIcrosoft is run by a bunch of C++ and Excel
idiots?

Aren't you dipshits tired of rebooting your fileservers in order to get
people out of your LDB files?

Arent' you guys tired of compact and repair?

Aren't you guys tired of crappy ETL?

SQL Server has about a billion ways to import text files into a
database.

It is just flat out more powerful; any way you look at it.

And no-- it really isn't any more complex than MDB.

Aren't you guys tired of refreshing and relinking and recreating linked
tables?

Aren't you guys tired of INDEXING?

SQL Server automates all of this stuff

I mean come on--- get real.

Any litttle sissy that sits there and claims that MDB is the future?

I challenge you to a good old-fashioned fist-fight.  Any time; you name
it.  I will throw down and break your friggin nose, mofos.  You are
destroying the lives of countless developers by encouraging the misuse
of MDB.

Any use of MDB in the year 2006 is MISUSE.  Completely unacceptable
ANYWHERE for ANY REASON.

sh.t; if i wasn't a convict (grass back in college), i would challenge
you to a real duel - like with pistols-- - for you MDB wimps spew
BLASPHEMY and you are destroying the lives of countless developers by
espousing the virtues of a crappy obsolete interface.

HOW MANY MDB SISSIES HAVE YOU MET?  It makes me want to cry; seeing
people with real skills that haven't introduced themselves to the
higher level of db programming.

MDB developers are a sad sad folk.

Aren't you guys tired of copying frontends and copying crap around??

Keep all your queries on the db server; they run FASTER.  They are more
POWERFUL.  And you can debug them and get real, intelligent error
messages.

SQL -- aka ADP-- is just a vastly superior product than these silly
little MDB files.

-Aaron