No, cached updates only changes the time for sending updates. Usually in InternalPost / InternalDelete but when you are using cache update, its when you call ApplyUpdates. Unless you are not using data aware controls. And you cached your record in a record / directly in your control and after that your close the dataset. Which is like the behaviour of using TClientDataset.
This problem happen because TDataset need "database component" still active when we read the data in that dataset. And when connection problem happen (ex: cable disconnected), the "database component" still active but it cannot communicate to the database server Winata David Smith wrote: > > even with older type TDatasets, I thought cached updates were the norm > which to my knowledge prevents from what you are describing from > happening. > > Dave > > --- On Sun, 8/31/08, winata <[EMAIL PROTECTED] > <mailto:win4t4%40telkom.net>> wrote: > > From: winata <[EMAIL PROTECTED] <mailto:win4t4%40telkom.net>> > Subject: Re: [delphi-en] Help!. Communication link failure > To: [email protected] <mailto:delphi-en%40yahoogroups.com> > Date: Sunday, August 31, 2008, 11:46 PM > > It's not about trapping error. If we are using dataset which is opened > when the link down (ex: cable disconnected) . > This would make a deadlock situation. Your dataset still active but you > cannot do anything to it. If you try to close it, it will > generate error (which mean you cannot close the dataset, even if you are > trapping the error) and you cannot take value from its field, > scroll the dataset to another record, etc > > So the only solution I know is using TClientDataset, using this solution > we only need a connection when we retrive or saved data. > Using this kind of solution we never go into deadlock situation. > > Winata > > NB : sorry about my english > > David Smith wrote: > > are you trapping the error with something like the following so the > app. can recover gracefully? > > > > try > > commLink.open; > > except > > showmessage( 'link seems to be down, try again later'); > > end; > > > > > > [Non-text portions of this message have been removed] > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.138 / Virus Database: 270.6.14/1644 - Release Date: 8/31/2008 > 4:59 PM >
