G
Guest
Are there any recent software updates that enhance the functionality of
these two products working together?
these two products working together?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
Sylvain Lafontaine
No and in my opinion, don't expect one.
B
Baz
Are there any recent software updates that enhance the functionality of
these two products working together?
It appears that, although ADP's will continue to exist in Access 2007, their
use will be deprecated. In other words, there will probably NEVER be any
more enhancements. It's a good time to revert to old fashioned ODBC linked
tables, if you haven't gone too far down the ADP route.
Good old Microsoft, this week's new best toy is on next week's scrapheap,
just like ADO.
A
aaron.kempf
BUNCH OF LYING ASSHOLES
ADP _WILL_ be updated in Access 2007.
ADP _HAS_ been updated many times over the past 7 years.
ADO isn't on the scrap heap.
DAO IS DED.
ADP _WILL_ be updated in Access 2007.
ADP _HAS_ been updated many times over the past 7 years.
ADO isn't on the scrap heap.
DAO IS DED.
A
aaron.kempf
Baz
you are such a lying asshole.. why do you spread mis-information??
you are such a lying asshole.. why do you spread mis-information??
A
aaron.kempf
MDB is the one that is being depecrated-- just as much as adp is.
technically, both MDB and ADP are being depecrated and then the new
XML-based ACCDB format will replace both of them
but i've seen it --straight from a microsoft access product manager--
than ADP is fully supported and will introduce support for SQL 2005
upon release
-Aaron
technically, both MDB and ADP are being depecrated and then the new
XML-based ACCDB format will replace both of them
but i've seen it --straight from a microsoft access product manager--
than ADP is fully supported and will introduce support for SQL 2005
upon release
-Aaron
D
dbahooker
SBAZ and SYLVAIN are full of crap.
ADP is fully supported; MDB is for IDIOTS and RETARDS.
the next version of Access, Access 2007 will continue support for ADP
on an equal footing with support for MDB.
to be honest; both MDB and ADP are going away-- in favor of ACCDB; but
it will have similiar SQL-based value.
keep everything in SQL; MDB is for idiots
-Aaron
ADP Nationalist
ADP is fully supported; MDB is for IDIOTS and RETARDS.
the next version of Access, Access 2007 will continue support for ADP
on an equal footing with support for MDB.
to be honest; both MDB and ADP are going away-- in favor of ACCDB; but
it will have similiar SQL-based value.
keep everything in SQL; MDB is for idiots
-Aaron
ADP Nationalist
B
Baz
Dear oh dear oh dear. And you a "senior SQL developer" too. A senior
5-year-old more like. Grow up.
5-year-old more like. Grow up.
A
aaron.kempf
SBAZ
ITS THE TRUTH; STRAIGHT OUT OF MICROSOFTS MOUTH!!!
-Aaron
ADP Nationalist
ITS THE TRUTH; STRAIGHT OUT OF MICROSOFTS MOUTH!!!
-Aaron
ADP Nationalist
B
Baz
So why, as you yourself said on another thread, does Microsoft need to be
pushed by MVP's to remain committed to ADP's?
By going down the ADP route, you made the wrong choice, as did I (all my new
developments for several years have been ADP's). It's not your fault, or
mine, we weren't to know that Microsoft was going to turn another one of
it's infamous somersaults. But, we are where we are, and the most
constructive approach is to plan a way forward from here. Screaming and
mewling like a spoilt brat will get you nowhere.
pushed by MVP's to remain committed to ADP's?
By going down the ADP route, you made the wrong choice, as did I (all my new
developments for several years have been ADP's). It's not your fault, or
mine, we weren't to know that Microsoft was going to turn another one of
it's infamous somersaults. But, we are where we are, and the most
constructive approach is to plan a way forward from here. Screaming and
mewling like a spoilt brat will get you nowhere.
L
larpup
Question: I have not yet decided on ODBC or ADP. One thing for sure, I
don't want to put time and resource into a tech. that will be passe' in
a few years.
What is the down side of ODBC? Will there be serious performance
issues? I will be building an app for 50+ users with thousands of
records. Performance is a very important piece to my decision. I would
like to use Access as my front end.
Any information regarding the above will be greatly appreciated.
Lar
don't want to put time and resource into a tech. that will be passe' in
a few years.
What is the down side of ODBC? Will there be serious performance
issues? I will be building an app for 50+ users with thousands of
records. Performance is a very important piece to my decision. I would
like to use Access as my front end.
Any information regarding the above will be greatly appreciated.
Lar
B
Baz
Unfortunately all of the existing technologies will be deprecated in Access
2007. If you need to use a server database engine (as you clearly do)
Microsoft appears to be recommending the new accdb Access format with linked
tables.
Although this isn't the same as the current setup of an mdb with linked
tables, it appears to me to be more like that than an ADP, and so that's the
route I would go for now. I don't think that waiting for Access 2007 is an
option, because major Access upgrades have a history of being pretty
disappointing for a release or two until the glitches get ironed out.
There should not be performance issues with ODBC linked tables. The main
thing to watch out for is that it is possible to create Jet queries that the
server is incapable of running. In these circumstances, Jet will run the
query itself, potentially dragging huge amounts of data from the server in
order to do so. The performance hit when this occurs is usually obvious,
and can be confirmed by using the SQL Profiler (assuming we're talking SQL
Server here). It's then generally pretty easy to modify the query so that
it gets executed by the server, or create it as a passthrough query.
2007. If you need to use a server database engine (as you clearly do)
Microsoft appears to be recommending the new accdb Access format with linked
tables.
Although this isn't the same as the current setup of an mdb with linked
tables, it appears to me to be more like that than an ADP, and so that's the
route I would go for now. I don't think that waiting for Access 2007 is an
option, because major Access upgrades have a history of being pretty
disappointing for a release or two until the glitches get ironed out.
There should not be performance issues with ODBC linked tables. The main
thing to watch out for is that it is possible to create Jet queries that the
server is incapable of running. In these circumstances, Jet will run the
query itself, potentially dragging huge amounts of data from the server in
order to do so. The performance hit when this occurs is usually obvious,
and can be confirmed by using the SQL Profiler (assuming we're talking SQL
Server here). It's then generally pretty easy to modify the query so that
it gets executed by the server, or create it as a passthrough query.
L
larpup
Thanks so much for the advice,
Lar
Lar
Unfortunately all of the existing technologies will be deprecated in Access
2007. If you need to use a server database engine (as you clearly do)
Microsoft appears to be recommending the new accdb Access format with linked
tables.
Although this isn't the same as the current setup of an mdb with linked
tables, it appears to me to be more like that than an ADP, and so that's the
route I would go for now. I don't think that waiting for Access 2007 is an
option, because major Access upgrades have a history of being pretty
disappointing for a release or two until the glitches get ironed out.
There should not be performance issues with ODBC linked tables. The main
thing to watch out for is that it is possible to create Jet queries that the
server is incapable of running. In these circumstances, Jet will run the
query itself, potentially dragging huge amounts of data from the server in
order to do so. The performance hit when this occurs is usually obvious,
and can be confirmed by using the SQL Profiler (assuming we're talking SQL
Server here). It's then generally pretty easy to modify the query so that
it gets executed by the server, or create it as a passthrough query.
A
aaron.kempf
BECAUSE ADP IS A SUPERIOR SOLUTION
BECAUSE THE MVPS ARE THE ONES WITH THE POWER TO CHANGE THINGS
I've known-- since Day 1-- that Microsoft wasn't going to turn a
somersault.
THEYVE COME OUT AND STATED IT IN PLAIN ENGLISH!!
ADP WILL BE SUPPORTED IN 2007. IT IS SUPPORTED TODAY.
BECAUSE THE MVPS ARE THE ONES WITH THE POWER TO CHANGE THINGS
I've known-- since Day 1-- that Microsoft wasn't going to turn a
somersault.
THEYVE COME OUT AND STATED IT IN PLAIN ENGLISH!!
ADP WILL BE SUPPORTED IN 2007. IT IS SUPPORTED TODAY.
A
aaron.kempf
Sbaz;
you are a liar and a retard.
'there shouldnt be performance issues with odbc linked tables'
THEN WHAT ABOUT STABILITY, CONCURRENCY, EASE OF DEVELOPMENT AND
MAINTENANCE?
ADP wins in _EVERY_ regard.
It is faster, easier to develop, easier to manage.
Lose the training wheels you fucking retards.
MDB is for fucking babies.
ADP won the war.
-Aaron
you are a liar and a retard.
'there shouldnt be performance issues with odbc linked tables'
THEN WHAT ABOUT STABILITY, CONCURRENCY, EASE OF DEVELOPMENT AND
MAINTENANCE?
ADP wins in _EVERY_ regard.
It is faster, easier to develop, easier to manage.
Lose the training wheels you fucking retards.
MDB is for fucking babies.
ADP won the war.
-Aaron
A
aaron.kempf
baz;
and for the record; this is the FIRST thing that you've said that isn't
complete hogwash.
MDB _AND_ ADP are going away.
but ADP-like functionality will still be completely supported in the
new ACCDB format.
It is currently there; I mean.. have you used Access 2007?
I've seen it IN WRITING, from Microsoft-- that DAPs will be supported
through the end of 2013.. and ADP will be supported in the next version
of Access; and the version after that.
-Aaron
and for the record; this is the FIRST thing that you've said that isn't
complete hogwash.
MDB _AND_ ADP are going away.
but ADP-like functionality will still be completely supported in the
new ACCDB format.
It is currently there; I mean.. have you used Access 2007?
I've seen it IN WRITING, from Microsoft-- that DAPs will be supported
through the end of 2013.. and ADP will be supported in the next version
of Access; and the version after that.
-Aaron
A
aaron.kempf
ARE YOU SERIOUSLY RECCOMENDING THAT THEY UNDERSTAND THE NUANCES BETWEEN
JET-SQL AND TSQL?
what a retarded reccomendation.
a) dont use JET
b) **** MDB format
c) spit on anyone that still uses it
d) use Access Data Projects
e) rinse and repeat
JET-SQL AND TSQL?
what a retarded reccomendation.
a) dont use JET
b) **** MDB format
c) spit on anyone that still uses it
d) use Access Data Projects
e) rinse and repeat
D
dbahooker
http://blogs.msdn.com/access/archive/2005/11/01/488022.aspx
ADP's and Access 12 Security:
The ADP architecture is conceptually unchanged between Access 2003 and
Access12, which means that the features continue to work in essentially
the same way they did. We continue to believe that SQL Server makes a
great store for Access data and that building the UI either through
linked tables or ADPs will continue to work well.
ADP's and Access 12 Security:
The ADP architecture is conceptually unchanged between Access 2003 and
Access12, which means that the features continue to work in essentially
the same way they did. We continue to believe that SQL Server makes a
great store for Access data and that building the UI either through
linked tables or ADPs will continue to work well.
A
aaron.kempf
ODBC linked tables?
for thousands of records and 50+ users?
ROFL
MDB linked tables start giving locking problems with only a single user
-Aaron
for thousands of records and 50+ users?
ROFL
MDB linked tables start giving locking problems with only a single user
-Aaron
A
aaron.kempf
thousands of records?
50 users?
ROFL
ODBC and MDB linked tables sucks balls. It starts causing locking
problems with only a single user
-Aaron
50 users?
ROFL
ODBC and MDB linked tables sucks balls. It starts causing locking
problems with only a single user
-Aaron
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.