By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,771 Members | 1,685 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,771 IT Pros & Developers. It's quick & easy.

23 Feb 2004, Solution/tunning for "Time Out Expired" , Server2000, connection object

P: n/a


We developed an application that has many data entry forms and data
controls in and Sql Server2000 as backend.
For this application we created connection object on load event of every
form. The application runs on Server machine with no errors.
We got some errors when the application/.exe run on client node, There is
no error till log-in happens, the log-in form uses connection object. After
that , when we click to open any form , typically we got error as "time out
expired". It seems it is happening when application starts fetching data
from Sql Server on server machine.

Any suggestions , comments and help are welcome.

We are not sure whether this is happening because of connection objects
created on every new form that user clicks.

Which one will take least resources and more reliable, faster
a. Create Connection object globally.
b. Create Connection object for every form that needs data connection.

Other Details :

Operating System : Windows Xp
Development Platform : Visual Trial Edition
Database : Sql Server 2000(Mixed Mode is enabled)

Thanks in advance for your help.

[Sham Shrinivas Yemul]
Visit following web site for Colored flame lamps

Intellisoft Computer Consultants Pvt. Ltd.
340 A Sakhar peth, Solapur - 413005
Phone : 91-(0)217-262 4713
Email : ye***
Jul 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.