Re: Run-time error 2147217841 Query Timeout expired

Tech-Archive recommends: Fix windows errors by optimizing your registry

Without seeing all of your code, I'd guess you are getting a time out on
your connection object. Are you opening and closing your connection on each
hourly call, or are you opening the connection once at the beginning of your
app, and expecting to stay alive whilst the app is sleeping between hourly
updates?

Ron W
"jonny" <nelsonj4@xxxxxxxxxxx> wrote in message
news:1185410793.361958.199220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am gettting a error message when I update a record set:

Using VB 6 and SQL Server express:

Every hour I call a sub routine that performs the code below. Works
great the first hour but the second hour it locks up and gives me an
error message "Query timeout expired".


With mrsAutoData

mrsAutoData.Requery
mrsAutoData.MoveLast

!rawdataid = frmrawdata.txtIDMain
!productionarea = frmrawdata.ctlProductionArea
!workstation = frmrawdata.ctlworkstation
!Date = Now
!shift = frmrawdata.txtShift
!Hour = frmrawdata.cboHourChoice
!hr1uptime = TimeAsMinutes1
!hr2uptime = TimeAsMinutes2



.Update

End With

Please help...



.

Relevant Pages

  • Re: global connections
    ... you should be opening and closing it when you need it. ... you create a single pipe through which all of your data ... Using C#, would it be best to have a global> connection and datareaders etc, or is it better to put all the db stuff> into a seperate class and make calls to this whenever I need to> read/amend data? ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Error with automated execution
    ... > I am opening a connection on a shared db as below which works fine when ... > in a vb.net win app. ... > standalone PC then that works. ... So apparently db connection have ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Error with automated execution
    ... | in a vb.net win app. ... | standalone PC then that works. ... So apparently db connection have different ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Run-time error 2147217841 Query Timeout expired
    ... Are you opening and closing your connection on each ... app, and expecting to stay alive whilst the app is sleeping between hourly ...
    (microsoft.public.vb.general.discussion)
  • Re: Memory problem - writing to database
    ... > take a lot of resource to keep opening and closing the db connection? ... I'm not even sure that ADO classic doesn't have a clever form of connection ... I also strongly suspect that by ... Don't worry about the fact that you're constantly opening new connections - ...
    (microsoft.public.vb.general.discussion)