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]> wrote: From: winata <[EMAIL PROTECTED]> Subject: Re: [delphi-en] Help!. Communication link failure To: [email protected] 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]
