Re: Access 2005, Adp and SQL Server

Larpup

Because I've been using it every day for 7 years; and it's the best db
IDE _ANYWHERE_

I am passionate about it; because someone needs to stick up for it.
People constantly spread mis-information about it.. and I've not read a
single advertisement from MS that says 'Use ADP'

I've got a laundry list of 20 bugs in ADP that Microsoft won't fix.

I got fired from Microsoft-- multiple times-- for complaining about
bugs in SQL and ADP.

I just know-- first hand-- that query analyzer is a better development
tool than Access MDB.
Too many times in MDB I have unexplained CRAP.
Too many times in MDB have I stacked queries on top of queries; just to
have it crap out.

it's ridiculous

If you have a properly designed MDB / Linked table solution..how much
code do you need to WRITE to change the database server?

I'm just not talking about Linked Table Manager.. I'm thiking about the
connection strings on SQL-passthru for example.

what.. do you expect every single person in the world to write similiar
code?

ROFL

I can change a connection in a single place.
If i want to bind a form to a sproc; I dont need to use DAO. I don't
need to do jack ***.. I can bind parameters from a sproc-- to form
controls.

Does Access MDB even support sprocs in SQL Server?
what if multiple people need to change a query at the same time?

What if a single user wants 2 versions of the frontend open at the same
time?

MDB just flat out sucks balls.

I would rather take double-penetration; in the ass in prison -- than
sit around and let you lazy fat stupid MDB slobs to sit there; another
day-- and think that MDB is a viable solution. MDB is DED. DAO is DED.

ADP runs circles around you lat lazy retards that are still stuck in
the 90s.

And I would rather that SOMEONE reads my complaints.

The squeky wheels gets oiled, MOFO.

-Aaron
ADP Nationalist


larpup wrote:
Aaron,

Why do you get so upset and display this behaviour on the forum? I am
just learning about SQL Server it's ability to interface with Access. I
would appreciate some intelligent, unemotional recommendations
regarding such. I called Microsoft and they were nice enough to send
me the link which I posted so others like myself, can investigate the
best choices.

I would appreciate some realistic reasons why you feel ADP would be the
better choice. Supported reasons that is. Frustrated name callings
don't really sway me or probably anyone else towards your obvious
goals. So, if you'd like, please feel free to address this issue in a
more suitable manner.

Lar



aaron.kempf@xxxxxxxxx wrote:
this is the BEST FEATURE in ADP but Microsoft somehow describes it as a
handicap?

Access Data Projects (ADPs)
An Access Data Project is an OLE document file, like the .xls or.doc
file formats. It contains forms, reports, macros, VBA modules, and a
connection string. All tables and queries are stored in SQL Server. The
ADP architecture was designed to create client-server applications.
Because of this, there is a limit to the number of records that Access
returns in any recordset. This limit is configurable, but you will
typically need to build a lot of filtering into your application to
avoid hitting the limit.



dipshits; someone in Redmond needs to start pushing ADP; ACCDB; Linked
tables.. 'local queries'

wtf are you talking about kids; friggin sellouts

ADP is 100 times simpler to manage

-Aaron


Brendan Reynolds wrote:
Thanks Lar, that's a very useful link.

BTW: You mean Access 2007, right? :-)

--
Brendan Reynolds
Access MVP

"larpup" <larpup@xxxxxxxxx> wrote in message
news:1158799903.111908.65890@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I don't know if this was posted prior, but it was recently sent to me
from Microsoft regarding A2005 & sql server as well as other pertinent
info..

http://technet2.microsoft.com/Office/en-us/library/1dce641e-ba1c-446a-8ff2-221769a58ba51033.mspx?mfr=true


Lar


.

Loading