Gustav Brock
gustav at cactus.dk
Sat Aug 20 12:53:12 CDT 2005
Hi Shamil First, welcome back to AccessD! Then, I find this a very interesting topic with a lot of perspective. /gustav >>> shamil at users.mns.ru 18-08-05 1:28 >>> 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