[AccessD] Disconnected MS Access cient applications..

Shamil Salakhetdinov shamil at users.mns.ru
Thu Aug 18 06:45:56 CDT 2005


No, William, this is not replication - here is what I mean in short:

http://www.smsconsulting.spb.ru/shamil_s/articles/ddo.htm

Shamil

----- Original Message ----- 
From: "William Hindman" <dejpolsys at hotmail.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Thursday, August 18, 2005 3:47 AM
Subject: Re: [AccessD] Disconnected MS Access cient applications..


> Shamil
>
> ..I must be missing something ...that sounds like replication to me.
>
> William
>
> ----- Original Message ----- 
> From: "Shamil Salakhetdinov" <shamil at users.mns.ru>
> To: "!DBA-MAIN" <accessd at databaseadvisors.com>
> Sent: Wednesday, August 17, 2005 7:28 PM
> 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




More information about the AccessD mailing list