> If we are using the application and a problem of communication with > the server occurs (network disconnection, Band width saturation, > etc.), our application didn't respond and show us a message > like "Communication Link Failure Error". When communication problem > is fixed problem persist. ... > Do you know if exist a way to continue working after a communication > problem occurs ?
Yes. By mirroring your database in local datasets and using these instead of the actual datasets in your SQL Express. TClintDataset has been designed just for that. Think of your SQL Express database as a server to which you connect only to update your local datasets, or server database, and always free your connection after usage. My bet is that you are using your connection as a permanent bridge between your application and your database. > I have an application for win32 developed on Delphi 7.0 and accessing > SQL Server 2005 Express database connecting to it using an ODBC > Connection. Wouldn't it be faster to use a SQL Native Client driver instead of ODBC? HTH. Emmanuel
