Guest Rick Lipkin Posted August 7, 2007 Posted August 7, 2007 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 off site 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 ?? I do not know if this is a server permissions issue where Win2003 breaks the ADO connection string .. just curious if anyone has had this issue and if there is a Server fix. Hope that makes sense. Any help would be appreciated. Rick Lipkin SC Dept of Health, USA
Recommended Posts