ADO sqloledb won't connect running on Win2003 server
- From: "Rick Lipkin" <lipkinrm29063@xxxxxxxxx>
- Date: Tue, 7 Aug 2007 19:20:56 -0400
To All
I have a wierd situation where I have a very successful ADO xHarbour\FWH C++
application ( executable ) which resides on a Win2003 server.
When the users run the executable from the server ( shortcut on their pc )
the application connects to the SQL server and runs flawlessly.
However .. if you are at the server console ( physically at the server ) ..
and you run the same application ( on the server ) it will start but fail to
connect to the first table.
Totally exhausted here trying to find an answer .. I have found Google ideas
on adding Persistant Security Info=False to no avail.
Here is the connection string :
oRs := TOleAuto():New( "ADODB.Recordset" )
oRs:CursorType := 1 // opendkeyset
oRs:CursorLocation := 3 // local cache
oRs:LockType := 3 // lockoportunistic
cSQL := "SELECT * FROM utility WHERE progid ='"+xPROGID+"'"
TRY
oRS:Open(cSQL,'Provider='+xPROVIDER+';Data Source='+xSOURCE+';Initial
Catalog='+xCATALOG+';User Id='+xUSERID+';Password='+xPASSWORD )
CATCH oErr
MsgInfo( "Error in Opening UTILITY CRASH BURN table" ) /// dies here
RETURN NIL
END TRY
Again .. this app runs the executable flawlessly as a shortcut on the
workstation .. but the same app will not run sitting at the server running
the app ON the server ??
Hope that makes sense. Any help would be appreciated.
Rick Lipkin
SC Dept of Health, USA
.
- Prev by Date: Re: SQL Server Specific Windows Firewall Exception
- Next by Date: RE: Linked server strangeness in SQL 2005 Mgmt Studio
- Previous by thread: Re: How to specify an instance name in a SQL statement
- Next by thread: RE: Unable to connect to SQL 2000 engine on other machine from SSM
- Index(es):
Relevant Pages
|
Loading