FiveTech Software tech support forums

... made a change in the server and we have changed mysql by sql server and we have follow problem: [CODE] oApp:oCon:ConnectionString:= "Provider=SQLOLEDB;Password=xxxx3;Persist Security Info=True;User ID=XXXX;Initial Catalog=ERP6_base;Data Source=185.80.87.6\SQLEXPRESS2019" TRY oApp:oCon:Open() ...

... loco me da error en el recordset, os paso como lo hago a ver si a alguien se le ocurre el porqué: oApp:oCon:ConnectionString:= "Provider=SQLOLEDB;Password=xxxx3;Persist Security Info=True;User ID=XXXX;Initial Catalog=ERP6_base;Data Source=185.80.87.6\SQLEXPRESS2019" TRY oApp:oCon:Open() ...

... loco me da error en el recordset, os paso como lo hago a ver si a alguien se le ocurre el porqué: oApp:oCon:ConnectionString:= "Provider=SQLOLEDB;Password=xxxx3;Persist Security Info=True;User ID=XXXX;Initial Catalog=ERP6_base;Data Source=185.80.87.6\SQLEXPRESS2019" TRY oApp:oCon:Open() ...

... "MSSQL",    "OLEDB", { "MSOLEDBSQL", "SQLNCLI11", "SQLNCLI10", "SQLNCLI", "SQLOLEDB" }, "" }, ;{ "MYSQL",    "ODBC",  { "Provider=MSDASQL;Driver={MySQL ODBC 8.0 ANSI ...

... JACGSOFT ]************************** // Function Connect_Sql(_Cnx_,_Usu_,_Cla_) Local _Cadena_,_Lg_:=.T. _Cadena_:='Provider=sqloledb;Data Source=168.1.0.80;'+ ; 'Network Library=DBMSSOCN;'+ ; 'Initial Catalog=BD_PRUEBA;User Id='+_Usu_+ ; ';Password='+_Cla_+';' _Cnx_:=Toleauto():New("ADODB.Connection") ...

Javier I still like Sqloledb for Sql Server .. I know Microsoft has been telling us for years that oledb will be depreciated ... and that was 5 or 6 years ago .. nice thing about using Sqloledb is that the client is already part of ...

... lDebug := IF(EMPTY(cDebug),.F.,.T.) cRoot := "" cTitle := "CDM Web Freight Data Integration" xPROVIDER := "SQLOLEDB" xSOURCE := "x" xDATABASE := "x" xUSERID := "x" xPASSWORD := "x" // Init... SET DATE FORMAT TO ...

... target computer. For example, any of these providers could be installed on your client's computer viz, SQLNCLI11, SQLNCLI10,SQLNCLI or the default SQLOLEDB. FWH function searches for the latest provider (driver) installed and establishes connection. This is a sample of our recommended usage:   ...

... target computer. For example, any of these providers could be installed on your client's computer viz, SQLNCLI11, SQLNCLI10,SQLNCLI or the default SQLOLEDB. FWH function searches for the latest provider (driver) installed and establishes connection. This is a sample of our recommended usage:   ...

... si me pueden ayudar como realizar la conexión, la cadena que me entrega Microsoft no funciona remplazándola directamente. w_sql='Provider=sqloledb;Server=tcp:siscont.database.windows.net,1433;Initial Catalog=prueba;Persist Security Info=False;User ID={marcelo};Password={C12345678};MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection ...

... , ; cEol := CHR(13) + CHR(10) , ; cSource := "c:\xml\inbox\" , ; cHistory := "c:\xml\inbox\history\" , ; xPROVIDER := "SQLOLEDB" , ; xSOURCE := "9.9.9.9" , ; xDATABASE := "DB-NAME" , ; xUSERID := "USERID" , ; xPASSWORD := "PASSWORD" ...

Thanks Rick, Well after considerable headaches, I found the problem. There was a Microsoft Security Essentials update that went wrong and basically messed up all my security settings. Once I removed it and re-installed, everything came back to normal. What a pain the B..... Thanks for your input and...

Darrell

Google JavaRA .. this is the java removal tool from MajorGeeks or Softpedia. This will remove all Java traces, folders and reg files.

Once Java has been removed .. get the latest version from Java.com .. Hope that helps.

Rick Lipkin

Hi Rick, It is very, very strange. I am able to run without a problem on any other workstation except mine which is the development machine. I honestly think is has to do with a Java update somehow. I removed Java and now getting strange errors when trying to install. "Computer not connected to...

Darrell Can you be a bit more specific on the error .. your code seems simple enough. Has anything changed on the Sql Server end ? Any field changes that would cause your query to fail ? Has your connection terminated or any new code injected before your Sql Command that may have effected the connec...