What is ADP and what it stands for?

  • Thread starter Thread starter Guest
  • Start date Start date
Hi. What is ADP and what it stands for?

Access Data Project.

An ADP is an Access application bound to a MS SQL Server database.
 
Hi,

ADP = Access Data project

One ot that sort of very good ideas, which are on the long run "die of
thirst - by MS marketing"
It is tied to Access 2003 and SQL Server 2000 - not particulary useful to
start with it now, as it not longer developed further.

read

http://www.databaseadvisors.com/gazette/sqlexpress.htm

and from the Microsoft access blog

" ...called ADPs or .adp files, provide an alternative to using the Access
database engine by allowing an Access application to connect directly to the
tables in a SQL Server database. ADPs will continue to be supported in
Office Access 2007. To take maximum advantage of the new features in Office
Access 2007, Microsoft recommends the use of linked tables to connect to SQL
Server data. ..."

also interesting read

http://blogs.msdn.com/access/archive/2006/04/25/583584.aspx

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

http://blogs.msdn.com/access/archive/2005/11/01/488022.aspx
 
hey you stupid ****ing german; why don't you start giving the full
story?

who said that they are 'dying by thirst'

when was the last time that you saw a MDB commercial?

why dont' you take your biased conclusions and shove them up your fat
german ass

-Aaron
 
note the presence of the word DIRECTLY

The Access application development tools can be used either with the
Access database engine or directly with the SQL Server database engine.

ACCDB is going to have something similiar to ADP functionality; you
build your shit in ADP today; you migrate it to ACCDB and you'll be
better off than ANY fat lazy retard german that can't pull the swastika
out of his ass far enough to grow some balls and learn SQL Server
 
The Access application development tools can be used either with the
Access database engine or directly with the SQL Server database engine.
 
and the funny part?

In Access 2003, a significant advance occurred when Microsoft
introduced drivers that connect to data stored in Windows SharePoint
Services. This was significant because these drivers call a component
that sends and receives SOAP messages to the Web Services interfaces in
Windows SharePoint Services. By enabling users to link to SharePoint
lists, Access allows queries, forms, and reports to treat SharePoint
lists as if they were standard relational tables.

these same dipshits think that SPS support in Access is a feature?

it's a BUG.
the worst; slowest option ANYWHERE.

has anyone tried to push 5,000 records into Sharepoint?


ROFL

idiots; grow some balls and learn SQL Server. It's won the war.

-Aaron
 
and for the record; you ****ing NAZI

http://blogs.msdn.com/access/archive/2006/04/25/583584.aspx#583728


# re: Better Looking Forms & Reports, Faster
Tuesday, May 02, 2006 1:24 PM by Clint
Yes. Beta 2 will support editing tables and views in SQL Server 2005 in
ADPs.

here it is; in plain english.

ADP 2007 supports SQL 2005.

Anything else that you want to imply?
anyone else that wants to make a reccomendation?

they can shove it up their ass.

is it my fault that MS is jerking off to a new format instead of
working on fixing their existing formats?

NO. If I had my way; MS would drop MDB and drop ACCDB and only put all
their efforts into ADP.

I mean.. do Oracle Forms work against DB2 data?

ROFL

-Aaron
 
Hello. It means that the best way to use access is using Qeries, forms,
reports and the tables linked to and SQL database? Is that right?

Once I thought about that, and I thought it was great.

Marco
 
Hi,
Hello. It means that the best way to use access is using Qeries,
forms, reports and the tables linked to and SQL database? Is that
right?

Once I thought about that, and I thought it was great.

"the best way" <uhh> i'm carefully about "best ways" as usually there are
many roads lead to Rome.

At least you can say that's the way MS suggests to go - if you look at that
Webcast about the convertion from Access to SQL Server 2005 here:

https://www118.livemeeting.com/cc/mseventsbmo/view?id=1032294932&role=attend&pw=C72805BD--mfgKlaus Oberdalhoff (e-mail address removed) unterstütze PASS Deutschland e.V. (http://www.sqlpass.de)
 
MDB or ACCDB with linked tables is utter CRAP.

use Access Data Projects.

SQL Server is a real database.. using MDB is insecure, unstable and
unreliable.

-Aaron
 
I disagree.

Just because some fat and lazy project manager at MS is too retarded to
learn SQL Server; does that mean that we should go back to DAO?

waffling on something like that is ridiculous.

I can do anything via ADO that you idiots can do in DAO. And I dont
have to rewrite EVERYTHING when I change databases.

-Aaron
 
Back
Top