[AccessD] Disconnected MS Access cient applications..

Jim,

I did also work disconnected but mainly bound way since MS Access 2.0.
This wasn't my wish - customer wanted that, or I'd better say they did have
a spec where diconnected mode was used, then they decided to use MS Access
2.0 as a development tool and then they found myself and I have had nothing
to do that implement this disconnedt mode in MS Access 2.0. It worked well.
Then I worked as a small team manager here and we used disconnected bound
solution with MS Access 97 for a big accounting project etc.

>  I think ADO.Net is the same thing but
> with an automatic transmission and slick features
ADO.NET and .NET Framework allow to implement this mode in a tiny framework,
which can be used from within MS Access or other applications. This isn't
possible with ADO - or I'd better say it's a complicated and time consuming
task if ADO is used.

> M$ has finally, fully embraced this concept and I feel that is
> where the next versions of Access are going.
My bet they will have that not in the next version of MS Access but the one
after it :)

Thank you for your sharing of your experience in this area and for your
opinion!
Shamil

----- Original Message ----- 
From: "Jim Lawrence" <accessd at shaw.ca>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Thursday, August 18, 2005 4:00 AM
Subject: RE: [AccessD] Disconnected MS Access cient applications..


> Hi Shamil:
>
> I have only (mostly) been using a style of disconnected ADO recordsets
with
> Access since 97-98. I use an Access FE for all sorts of DBs like Oracle/MS
> SQL, MySQL* (*though it needs an ODBC connection :-( ) and even MDB (but
> mostly just for temp files), singularly or in groups. The process is just
so
> fast, attaches through any reasonable connection and requires very few BE
DB
> licenses... clients save a bundle. I think ADO.Net is the same thing but
> with an automatic transmission and slick features. It should eliminate a
lot
> of coding. M$ has finally, fully embraced this concept and I feel that is
> where the next versions of Access are going.
>
> This is all my opinion of course and not meant to insight a riot.
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
> Salakhetdinov
> Sent: Wednesday, August 17, 2005 4:29 PM
> To: !DBA-MAIN
> Subject: [AccessD] Disconnected MS Access cient applications..
>
> Hi All,
>
> I wanted to ask you - what about the subject?
> Anybody uses/interested to use MS Access client applications this way?
>
> Do I miss obvious (RTFM) stuff and such a disconnected mode is already
> implemented in MS Access and broadly used by MS Access developers? Yes, I
> know ADO recordsets can be used with bound MS Access forms etc. but this
> looks like a rather limited feature - am I wrong?
>
> What I mean is cashing data locally into mdbs, only the data needed for
the
> currently open form(s) etc., processing this data and then updating
backend
> database(mdb, MSDE, MS SQL, whatever...) - with all this cashing and
> updating made mostly automatically by a tiny framework code, based on
> ADO.NET...(yes, this local caching of data is not a new subject but
nowadays
> it can be (re-)implement really scalable way with a way less efforts than
> before)
>
> Maybe MS plans to do something like that?
>
> Is that a wheel reinvention or anybody here sees such opportunity like a
> really useful feature in their real life projects?
>
> For me it looks like a useful feature because it could help: to get MS
> Access back into mainstream development area because it will allow to
easily
> scale applications with MS Access front-ends...
>
> There are many other ideas but most of them in this "ideas pool" based on
> the subject one - if it doesn't make sense for real-life projects then I'd
> better stop working on it...
>
> What is your opinion about the subject?
> When you expect MS will do something like that in MS Access?
>
> Thank you,
> Shamil
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com