Hi Jay,
We had similar issues over the years with MDI applications being run from Network Fileshares and accessing DBs.
Make sure that the client PC does not go into a sleep mode when idle. This used to shutoff the network activity and killed the DB connection for the applications. It tended to happen when users left their PC idle during lunch hour.
When users "woke-up" their PCs again the DB connection was dead and the applications would throw errors until they closed and reopened to establish a new connection.
The simplest solution was to disable the auto sleep feature in the PCs powersaving settings, which clients preferred, but as Chris mentions you could use a Hearbeat function to ping the DB server or to mimic some Client PC activity during idle time. Just make sure the Heartbeat triggers at shorter intervals than the Power Saving settings.
Michael
HI
Thanks for reply
but i don't know that this error taken how much time
means this error is accure after 15-25 min when i not using application or some time it happen after some different time
but exact time is needed in timer event