The future of ADP

S

Simon Minder

Hi all,

Does anybody know why ADP was not updated to the new format in 2007?

In additon, ADP seems not to be able to be integrated with SharePoint 2007
or BCM 2007. Has anybody experience with this?

Kind regards,

Simon
 
B

Brendan Reynolds

Simon Minder said:
Hi all,

Does anybody know why ADP was not updated to the new format in 2007?

In additon, ADP seems not to be able to be integrated with SharePoint 2007
or BCM 2007. Has anybody experience with this?

Kind regards,

Simon
Click to expand...


As far as I know, Microsoft have never made any official public announcement
on the future of ADPs. Personally, I looked at ADPs when they were
introduced in Access 2000, and thought that they were an interesting version
one technology - not yet ready for serious use, in my opinion, but with some
promising potential for future development. So I waited to see what
Microsoft would do with them in Access 2002. And the answer was, very
little. It seemed clear to me then that ADPs weren't going anywhere. This
conclusion was confirmed, for me, when Access 2003 was released, again with
few if any significant enhancements to ADPs. Access 2007 has merely
continued a trend that has been established for a number of years now.
 
A

Albert D. Kallal

Simon Minder said:
Hi all,

Does anybody know why ADP was not updated to the new format in 2007?
Click to expand...

I'm not really sure what you mean by not updated?

The new version of access was updated support some of the features, and
especially that of SQL server 2005. if you go to older versions of MS
access, they really don't 100% correctly work with newer versions of SQL
server (unless you put that SQL server into the old compatibility mode). So
therefore each new version of MS access that comes out, has in fact been
updated to work with the latest version of SQL server.

There's every indication that the access developer team remains committed to
ADP's as one viable solution in the many bag of tricks and faucets that the
great tool MS access gives to us devlopers.
In additon, ADP seems not to be able to be integrated with SharePoint 2007
Click to expand...

I'm not really worried about this. The integration of access 2007 into share
point via a standard accDB file was substantially improved over that in
access 2003. In fact, I think if you committed to a SQL server technology,
and you want to use a ADP, then that is just fine.

On the other hand, if you need to use share point, I don't really think
there's any special or particular relationship between that of a ADP and
that of SQL server.

It would have been a real sad day if we had to use a ADP to work with
SharePoint. ATP's have always been limited in their connection ability to
only SQL server, and that's just simply part of a decision you make when you
commit to using ADP's.

The fact matter is you have a lot more flexibility to use a standard
database file, and then you can choose to link to SQL server tables, local
tables, and yes now integration with SharePoint lists also (and, the could
have all those links active at the same time).

MS access does not have limitations in using differnt data sources and
diverse data sources if you choose a standard database file.

ADP's have always been limited to only connect into SQL server, and it does
not even support using other ODBC data sources, which is one of perhaps the
larger limitations of using ADP's. It does seem certainly true that there's
more investment dollars going into the regular version of access, but they
have been making some updates to ADP's to support later versions of SQL
server, they're just missing out on the new share point stuff.
 
D

David W. Fenton

In additon, ADP seems not to be able to be integrated with
SharePoint 2007 or BCM 2007. Has anybody experience with this?
Click to expand...

Since ADPs are designed as a front end to SQL Server and nothing but
SQL Server, how in the world could there be any integration at all
with SharePoint, which is *not* SQL Server?
 
P

(PeteCresswell)

Per Simon Minder:
why ADP was not updated
Click to expand...

Has anybody heard anything good about ADPs?

I've heard quite a few things - but I wouldn't call any of them
"good".
 
T

Tony Toews [MVP]

Albert D. Kallal said:
There's every indication that the access developer team remains committed to
ADP's as one viable solution in the many bag of tricks and faucets that the
great tool MS access gives to us devlopers.
Click to expand...

Committed is a strong word in my opinion. ADPs are still supported
but they haven't been enhanced in A2007. So supported is a word I'd
support. <smile>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
L

Larry Linson

(PeteCresswell) said:
Per Simon Minder:

Has anybody heard anything good about ADPs?

I've heard quite a few things - but I wouldn't call
any of them "good".
Click to expand...

There are those who think highly of them. I'm not one of those who do. I
did enough work with a client's ADP to confirm to my satisfaction that: the
ADP was usable, but had no compelling advantage over MDB with ODBC, as far
as I could determine.

Over the years, most of my clients/customers who've had client-server
databases also had a corporate standard server DB, which often was not
Microsoft SQL Server, but always was ODBC-compliant. Even if they did use MS
SQL Server, most wanted to "preserve their option to change their standard
server DBMS" (although I never had a customer who actually did so while I
was working with them).

Larry Linson
Microsoft Office Access MVP
 
R

Rick Brandt

Larry said:
There are those who think highly of them. I'm not one of those who
do. I did enough work with a client's ADP to confirm to my
satisfaction that: the ADP was usable, but had no compelling
advantage over MDB with ODBC, as far as I could determine.

Over the years, most of my clients/customers who've had client-server
databases also had a corporate standard server DB, which often was not
Microsoft SQL Server, but always was ODBC-compliant. Even if they did
use MS SQL Server, most wanted to "preserve their option to change
their standard server DBMS" (although I never had a customer who
actually did so while I was working with them).
Click to expand...

That was always the non-starter for me. As pervasive as dot-net is, if they
had brought that out and said that it could only build apps that connect to
SQL Server databases it would be just as dead as ADPs are. Most people
refuse to be that locked in.
 
Top