Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Connection is used by another hstmt.
Message
From
04/11/2004 11:36:14
 
 
To
04/11/2004 06:36:56
General information
Forum:
Visual FoxPro
Category:
Client/server
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
00957561
Message ID:
00958154
Views:
20
>>>>>>Original in German:
>>>>>>Datenbankfehler 0: [Microsoft][ODBC SQL Server Driver]Die Verbindung ist mit Ergebnissen von einem anderen hstmt belegt
>>>>>>
>>>>>>I Try to translate:
>>>>>>Databaseerror 0: [Microsoft][ODBC SQL Server Driver] Connection is used by another hstmt.
>>>>>The error occur into the a View or into a SPT command ?
>>>>>You can put the code piece that generates the error?
>>>>
>>>>The Error occur in an SPT command. The Code is difficult to write here, because of our Framework. Bud I try to:
>>>>
>>>>this.ConString	= "SERVER=Sql-server;DATABASE=ivs2000;TRUSTED_CONNECTION=Yes"
>>>>lcConName       = this.ConName
>>>>lcODBCDriver    = this.ODBCDriver
>>>>CREATE CONNECTION &lcConName CONNSTRING "DRIVER="+lcODBCDriver+";"+this.ConString
>>>>
>>>>lnConHdl = sqlConnect(this.ConName, .t.)
>>>>sqlsetprop(lnConHdl,"IdleTimeout",0)
>>>>
>>>>sqlExec(lnConHdl, "select max(aufneuanlage) as neuanlage from auftragseingang", "curTest")
>>>>
>>>>
>>>
>>>the line:
>>>
>>>CREATE CONNECTION (m.this.ConName) CONNSTRING ....
>>>
>>>redefine ConName at runtime.
>>>
>>>Difficult to say it with certainty,
>>>but task that if VFP has used this with a view, probably it has gone in confusion, or it is appeared a rare bug.
>>>The error has this meant:
>>>- VFP in a ODBC command has used a statement handle together
>>>to a incorrect session handle.
>>>
>>
>>Well, as I said it is difficult to show here the exact Programm code. Our APP is very compex. The create Connection command will only Fire if there is no connection in the DBC. So I think the Problem is at a nother point.
>>
>>
>>>A solution is that one to analyze the Log of the ODBC API commands.
>>Ok, where can I do this?
>
>Go into the Window Panel Control\Administration instruments\ODBC manager
>Analysis tab -> Start button ( before choice a File where the log it is written )
>then press Apply.
>ATTENTION : you have to do this only for the slot time where the problem exists,
>otherwise the txt audit file it can grow very quickly.
>After open the log file ( you can open it also during the log running)
>and search for the ODBC error string.
>
>If you have problems with this low level raw informations ( it is a API C inteface)
>you can cut the 20-30 APIs commands and post here.
>
>Fabio

It does not create an File. Might it be because we are using an DSN less Connection?

Jörg
Jörg Schneider
Joerg.Schneider@SMARTCRM.de
SMARTCRM CRM powered by MS Visual FoxPro
SMARTCRM GmbH
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform