accdb vs adp

"Tony Toews [MVP]" wrote in message
...
"a a r o n . k e m p f @ g m a i l . c o m"

Do you really think that it's efficient to manually copy queries in
and out of every front end every time you open the DB?

I don't see how this works.

Neither does anyone else on this planet.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

You can as easily set up a SQL-Server Express local to your machine and make
it synchronises over the Internet to a remote database and make it work in
both connected and disconnected mode. Instead of connecting the ADP to the
remote database, you connect it to the local SQL-Server. Not that much
different than your current scenario.

For the rest, SharePoint is a big table, not a database. If you can put
everything in a single table then that's fine but for connecting to an
existing database with multiple tables interconnected with relationships;
not so sure about that. Of course, you can start mixing up a solution on
the server like setting up some SSIS jobs in order to synchronise SharePoint
with the other database but then, bye bye the simplicity and say Hi! to the
costs.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
Independent consultant and remote programming for Access and SQL-Server
(French)


"Albert D. Kallal" wrote in message
...

"a a r o n . k e m p f @ g m a i l . c o m" wrote
in message
...
Can ACCDB work over wireless?

I dont' think so!


Yes it does. We have a new off line mode, and if the connection breaks,
you can continue using the local data store. When the connection is
restored...data again beings to sync. This feature was added to the new
ACE for use with disconnected SharePoint tables.

So, we talking about cached disconnected data.

And, over an intermitting connection that is constantly breaking and
re-connecting and disconnecting the application will continue to run. Data
is syncing much like a email send/receive type of model. You don't get
this ability with ADP, but you sure do with ACCDB over wireless when using
SharePoint as your data store.

This ability is a result of changes made to ACE (the new JET) engine.
Users of ADP can only dream about such functionally here.

It is possbile you not heard of this new thing called the internet.

With a future world of Smartphone's, Wi-Fi hotspots then it is a no brain
that we need technology that can work in these environments. This is
clearly one big future of our industry. Access has joined this new party,
but this feature is not available by using ADP's. It is with accDB


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

"a a r o n . k e m p f @ g m a i l . c o m"
wrote in

m:

-Aaron

Welcome back from jail, or parole, or whatever part of your
punishment for stalking/harassment has now reached its end, and
apparently now allows you to post your lies and misrepresentations
in public places without fear of retribution.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

"Tony Toews [MVP]" wrote in
:

"David W. Fenton" wrote:

But all of this will change 2-3 years from now, with the release
of Access 15, which apparently is going to address the neglect of
ADPs in the last two releases. That isn't enough to convince me
that it's wise to trash an MDB app and replace it with an ADP even
then, but it's worth keeping in mind (i.e., the investment in
moving to ADP could pay off 2 or 3 years down the road; on the
other hand, the Access 15 ADPs could be sufficiently different to
make current ADPs problematic).

I hadn't heard this. Any URLs?

Something somebody said somewhere (how's that for specific?) and a
post on the Access team blog:

Access 15 and SQL Server:
http://tinyurl.com/yffbdyt =
http://blogs.msdn.com/access/archive...15-and-sql-ser
ver.aspx

I'm trying to think where I heard the information about ADPs and
such, and am drawing a blank. I thought it was somewhere here in the
newsgroups, since I trusted the source (I wouldn't be passing it on
if I hadn't marked it as trusted in my memory).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Stalking / Harrassment.. uh, what are you talking about?

Legally, it never happened.

Thanks for your concern though!

-Aaron


On Feb 23, 2:20*pm, "David W. Fenton"
wrote:
"a a r o n . k e m p f @ g m a i l . c o m"
wrote
m:

-Aaron

Welcome back from jail, or parole, or whatever part of your
punishment for stalking/harassment has now reached its end, and
apparently now allows you to post your lies and misrepresentations
in public places without fear of retribution.

--
David W. Fenton * * * * * * * * *http://www.dfenton.com/
usenet at dfenton dot com * *http://www.dfenton.com/DFA/

ROFL oh that's cute dude!!!

Yah right, I'm sure it works as well as the rest of Jet does!!!

Tired of corruption?
Tired of bloat?

Move to ADP / SQL

-Aaron



On Feb 23, 11:26*am, "Albert D. Kallal"
wrote:
"a a r o n . k e m p f @ g m a i l . c o m" wrote in
...

Can ACCDB work over wireless?

I dont' think so!

Yes it does. We have a new off line mode, and if the connection breaks, you
can continue using the local data store. When the connection is
restored...data again beings to sync. This feature was added to the new ACE
for use with disconnected SharePoint tables.

So, we talking about cached disconnected data.

And, over an intermitting connection that is constantly breaking and
re-connecting and disconnecting the application will continue to run. Data
is syncing much like a email send/receive type of model. You don't get this
ability with ADP, but you sure do with ACCDB over wireless when using
SharePoint as your data store.

This ability is a result of changes made to ACE (the new JET) engine. Users
of ADP can only dream about such functionally here.

It is possbile you not heard of this new thing called the internet.

With a future world of Smartphone's, Wi-Fi hotspots then it is a no brain
that we need technology that can work in these environments. This is clearly
one big future of our industry. Access has joined this new party, but this
feature is not available by using ADP's. It is with accDB

--
Albert D. Kallal * *(Access MVP)
Edmonton, Alberta Canada

your autofeupdater runs progressively slower the more queries you
have.

keeping all your data and queries in one place- where they belong - on
a database server-- is a much more effective and efficient method.


On Feb 23, 10:54*am, "Tony Toews [MVP]"
wrote:
"a a r o n . k e m p f @ g m a i l . c o m"
wrote:

ADP is the best answer.

In a few scenarios sure.

Do you really think that it's efficient to manually copy queries in
and out of every front end every time you open the DB?

I don't see how this works.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
* updated seehttp://www.autofeupdater.com/
Granite Fleet Managerhttp://www.granitefleet.com/

neglect of ADP?

that never happened, kid!

there have been new features in ADP for every version for the past 5
versions.

there have been new features in SQL Server for every release for the
past 5 versions.

-Aaron




On Feb 23, 10:53*am, "Tony Toews [MVP]"
wrote:
"David W. Fenton" wrote:

But all of this will change 2-3 years from now, with the release of
Access 15, which apparently is going to address the neglect of ADPs
in the last two releases. That isn't enough to convince me that it's
wise to trash an MDB app and replace it with an ADP even then, but
it's worth keeping in mind (i.e., the investment in moving to ADP
could pay off 2 or 3 years down the road; on the other hand, the
Access 15 ADPs could be sufficiently different to make current ADPs
problematic).

I hadn't heard this. *Any URLs?

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
* updated seehttp://www.autofeupdater.com/
Granite Fleet Managerhttp://www.granitefleet.com/

"David W. Fenton" wrote:


But all of this will change 2-3 years from now, with the release
of Access 15, which apparently is going to address the neglect of
ADPs in the last two releases. That isn't enough to convince me
that it's wise to trash an MDB app and replace it with an ADP even
then, but it's worth keeping in mind (i.e., the investment in
moving to ADP could pay off 2 or 3 years down the road; on the
other hand, the Access 15 ADPs could be sufficiently different to
make current ADPs problematic).

I hadn't heard this. Any URLs?

Something somebody said somewhere (how's that for specific?) and a
post on the Access team blog:

Access 15 and SQL Server:
http://tinyurl.com/yffbdyt =
http://blogs.msdn.com/access/archive...15-and-sql-ser
ver.aspx

Oh yes, now I recall that posting.

I'm trying to think where I heard the information about ADPs and
such, and am drawing a blank. I thought it was somewhere here in the
newsgroups, since I trusted the source (I wouldn't be passing it on
if I hadn't marked it as trusted in my memory).

In that same blog posting:

"How often do create a ADP + SQL solution vs. a Access frontend linked
to SQL? In other words, how often is it about something like an ADP,
and how often do you work with linked SQL tables? Is one of these
more important for us to improve than the other?"

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

DSN and linked tables, and all that other junk-- is just a waste of
time.

It gives zero benefit over linked servers, for example






On Feb 23, 2:42*pm, "Tony Toews [MVP]" wrote:
"David W. Fenton" wrote:





But all of this will change 2-3 years from now, with the release
of Access 15, which apparently is going to address the neglect of
ADPs in the last two releases. That isn't enough to convince me
that it's wise to trash an MDB app and replace it with an ADP even
then, but it's worth keeping in mind (i.e., the investment in
moving to ADP could pay off 2 or 3 years down the road; on the
other hand, the Access 15 ADPs could be sufficiently different to
make current ADPs problematic).

I hadn't heard this. *Any URLs?

Something somebody said somewhere (how's that for specific?) and a
post on the Access team blog:

Access 15 and SQL Server:
http://tinyurl.com/yffbdyt=
http://blogs.msdn.com/access/archive...15-and-sql-ser
ver.aspx

Oh yes, now I recall that posting.

I'm trying to think where I heard the information about ADPs and
such, and am drawing a blank. I thought it was somewhere here in the
newsgroups, since I trusted the source (I wouldn't be passing it on
if I hadn't marked it as trusted in my memory).

In that same blog posting:

"How often do create a ADP + SQL solution vs. a Access frontend linked
to SQL? *In other words, how often is it about something like an ADP,
and how often do you work with linked SQL tables? *Is one of these
more important for us to improve than the other?"

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
* updated seehttp://www.autofeupdater.com/
Granite Fleet Managerhttp://www.granitefleet.com/