Quantcast
Channel: SQL Server Data Access forum
Viewing all 4164 articles
Browse latest View live

help me with LINQ statement to give IN clause in where condition

$
0
0

I have  the following model

DepotModelDepotNointDepotnamestring

DepotBreakLockDepotNoint[Column("isLocked")]publicbool isBreakLocked {get;set;}
[NotMapped]
DepotNamestringUserDepotLinkUserIdintDepotNoint

I want to get the  same sql given below  in LINQ  please help . The result  should be getting into the  Var 'Datalist'

varDatalist=
select A.DepotNo,A.DepotName,b.isLocked, CASE WHEN B.isLocked =1 THEN 'Closed' ELSE 'Open'END AS StatusfromDepot A left join BreakLogLock] B on A.DepotNo=B.DepotNowhere A.DepotNoin(selectDepotNofromUserDepotLinkwhere userid =3)


polachan


Traditional chinese charset support in SQL Server

$
0
0

Hi All:

Our customer is facing Traditional Chinese character display issue. most of the Chinese character can be displayed properly, however some less used chars are displaying '?', the column type if varchar(255), for some reason, we could not change it to nvarchar(255).

I found there are a few collations about traditional chinese, such as Chinese_Taiwan_Stroke_CS_AS or Chinese_Taiwan_Stroke_90_CS_AI or Chinese_Traditional_Bopomofo_100_CS_AS,are they referring to the same charset, or someone includes more characters? I'd like to find out one collation which support widest range of Tradition Chinese charset, is that possible? thanks in advance.

Kind regards


fight for future!

SQL 2016 SA account - Backup database

$
0
0
Good Morning Colleagues

I hope you are doing good . Regarding SQL server 2016 , Does the  SA account has the permissions to backup database ?

Best Regards

ODBC: SQLDescribeParam returns "NullablePtr" always set to 1

$
0
0

Hello everybody,

 

we are working on a software project using ODBC as SQL Server Data Access technology. The projects application builds complex SQL Statements dynamically. At some point we need to know if a column of such dynamical statement is nullable or not. Unfortunately,SQLDescribeParamalways returns “1” for its “Nullable” parameter.

 

I can reproduce this in a small C++ example (Windows Console App, please see end of this post.):

 

SQLDescribeParam returns “1” for Nullable[0] but SQLExecuteclaims

 

23000 Errorcode = 515

[Microsoft][SQL Server Native Client 11.0][SQL Server]Der Wert NULL kann in die

mycontentnotnull-Spalte, MS_C266513.dbo.Tab_266513-Tabelle nicht eingef³gt werden.

Die Spalte lõsst NULL-Werte nicht zu. Fehler bei INSERT.

 

Sorry for german language. Something like: The column does not allow NULL-Values

 

Alternatively I tried to fetch the information withSQLGetDescField.Same result. The IPD-Descriptor says the column “mycontentnotnull“ is nullable:

 

IPD

---

1 Records

 

 Record 1

 SQL_DESC_CASE_SENSITIVE : 0

 SQL_DESC_CONCISE_TYPE : 12

 SQL_DESC_DATETIME_INTERVAL_CODE : 0

 SQL_DESC_DATETIME_INTERVAL_PRECISION : 50

 SQL_DESC_FIXED_PREC_SCALE : 0

 SQL_DESC_LENGTH : 50

 SQL_DESC_NAME : ''

 SQL_DESC_NULLABLE : 1

 SQL_DESC_OCTET_LENGTH : 0

 SQL_DESC_PARAMETER_TYPE : 1

 SQL_DESC_PRECISION : 50

 SQL_DESC_SCALE : 0

 SQL_DESC_TYPE : 12

 SQL_DESC_TYPE_NAME : 'varchar'

 SQL_DESC_UNNAMED : 1

 SQL_DESC_UNSIGNED : 1

 

The Microsoft documentation forSQLSetDescField(Set, notGet) says:

 

„In IPDs, this field is always set to SQL_NULLABLE because dynamic parameters are always nullable and cannot be set by an application.

 

Astonishing, this behavior changed from SQL Server 2008 to SQL Server 2012. If you useeither the DBMS or‘the ODBC driver’ before SQL Server 2012, the nullable Parameter is returned as expected: “0”. Also the windows build in driver called “SQL Server” (sqlsrv32.dll) returns “0”, even on Windows 10 and even when connected to SQL Server 2012, 2014, 2016 or  2017. But the “ODBC Driver for SQL Server” (msodbcsql13.dll) and the “SQL Server Native Client” (sqlncli11.dll) returning “1” with those SQL Server.

 

My questions now are:

 

Am I doing something wrong?  

Do you feel, this is an issue in the mentioned SQL Server

      components, too?

Is Microsoft making things too easy when maintaining “this

        field is always set to SQL_NULLABLE because dynamic parameters

        are always nullable“

For me, the nullable information is significant important. Is

      there a change to get an official statement from Microsoft?

 

 

Thank you for your patience.

 

Finally the C++ example.

And thank you in advice for any suggestions.






#include "pch.h"
#include "Windows.h"
#include "Sql.h"
#include "Sqlext.h"
#include <iostream>
#include <assert.h>

// script to create table:
//
// CREATE TABLE[dbo].[Tab_266513](
//  [mycontentnotnull][varchar](50) NOT NULL
//  )
// GO



#define DSN_CONNECT_STRING  L"DSN=SQL2017;uid=camos;pwd=camos;"
#define SQL_STATEMENT       L"INSERT INTO TAB_266513(MYCONTENTNOTNULL) VALUES(?)"
wchar_t       UniBuffer[2048];

void ODBC_Err (HENV hODBC_, const char *location, HDBC hdlDBC_, HSTMT hdlStatement_)
{
  SQLSMALLINT   RecNumber, TextLength;
  SQLINTEGER    ErrCode = 0;
  RETCODE       retcode;
  wchar_t       Sqlstate[10];

  std::wcout << location << ":\n";

  RecNumber = 0;
  while (SQL_SUCCEEDED(retcode = SQLGetDiagRecW(SQL_HANDLE_ENV, hODBC_, ++RecNumber, Sqlstate, &ErrCode, UniBuffer, sizeof(UniBuffer) / sizeof(wchar_t), &TextLength)))
    std::wcout << Sqlstate << " Errorcode = " << ErrCode << "\n" << UniBuffer << "\n";

  if (hdlDBC_ != SQL_NULL_HDBC) {
    RecNumber = 0;
    while (SQL_SUCCEEDED(retcode = SQLGetDiagRecW(SQL_HANDLE_DBC, hdlDBC_, ++RecNumber, Sqlstate, &ErrCode, UniBuffer, sizeof(UniBuffer) / sizeof(wchar_t), &TextLength)))
      std::wcout << Sqlstate << " Errorcode = " << ErrCode << "\n" << UniBuffer << "\n";
  }

  if (hdlStatement_ != SQL_NULL_HSTMT) {
    RecNumber = 0;
    while (SQL_SUCCEEDED(retcode = SQLGetDiagRecW(SQL_HANDLE_STMT, hdlStatement_, ++RecNumber, Sqlstate, &ErrCode, UniBuffer, sizeof(UniBuffer) / sizeof(wchar_t), &TextLength)))
      std::wcout << Sqlstate << " Errorcode = " << ErrCode << "\n" << UniBuffer << "\n";
  }
  exit(1);
}

int main () {

  HENV          hODBC         = SQL_NULL_HENV;
  HSTMT         hStmt         = SQL_NULL_HSTMT;
  unsigned long ulODBCVersion = SQL_OV_ODBC3;
  HDBC          DBC_Handle    = SQL_NULL_HDBC;
  SQLSMALLINT   nCount        = 0;
  SQLSMALLINT   NumParams     = 0;

  if (!SQL_SUCCEEDED (SQLAllocHandle (SQL_HANDLE_ENV, SQL_NULL_HANDLE, &hODBC)))
    ODBC_Err (hODBC, "SQLAllocHandle SQL_HANDLE_ENV", SQL_NULL_HDBC, SQL_NULL_HSTMT);

  if (!SQL_SUCCEEDED (SQLSetEnvAttr (hODBC, SQL_ATTR_ODBC_VERSION, (SQLPOINTER) ulODBCVersion, 0)))
    ODBC_Err (hODBC, "SQLSetEnvAttr SQL_ATTR_ODBC_VERSION", SQL_NULL_HDBC, SQL_NULL_HSTMT);

  if (!SQL_SUCCEEDED (SQLAllocHandle (SQL_HANDLE_DBC, hODBC, &DBC_Handle)))
    ODBC_Err (hODBC, "SQLAllocHandle SQL_HANDLE_DBC", DBC_Handle, SQL_NULL_HSTMT);

  if (!SQL_SUCCEEDED (SQLDriverConnectW (DBC_Handle, NULL, (SQLWCHAR *) DSN_CONNECT_STRING, (SQLSMALLINT) wcslen (DSN_CONNECT_STRING), 
                                        UniBuffer, sizeof (UniBuffer) / sizeof (wchar_t), &nCount, SQL_DRIVER_NOPROMPT)))
    ODBC_Err (hODBC, "SQLDriverConnectW", DBC_Handle, SQL_NULL_HSTMT);

  if (!SQL_SUCCEEDED (SQLAllocHandle (SQL_HANDLE_STMT, DBC_Handle, &hStmt)))
    ODBC_Err (hODBC, "SQLAllocHandle SQL_HANDLE_STMT", DBC_Handle, hStmt);

  if (!SQL_SUCCEEDED (SQLPrepareW (hStmt, (SQLWCHAR *) SQL_STATEMENT, wcslen (SQL_STATEMENT))))
    ODBC_Err (hODBC, "SQLPrepareW", DBC_Handle, hStmt);

  if (!SQL_SUCCEEDED (SQLNumParams (hStmt, &NumParams)))
    ODBC_Err (hODBC, "SQLNumParams", DBC_Handle, hStmt);
  assert (NumParams == 1);




  SQLSMALLINT DataType[1], DecimalDigits[1], Nullable[1];
  SQLULEN     ParamSize[1];
  for (SQLUSMALLINT i = 0; i < NumParams; i++)
    if (!SQL_SUCCEEDED (SQLDescribeParam (hStmt, i + 1, DataType + i, ParamSize + i, DecimalDigits + i, Nullable + i)))
      ODBC_Err (hODBC, "SQLDescribeParam", DBC_Handle, hStmt);

  const wchar_t Empty[] = L"";
  SQLLEN        Empty_Length = (Nullable[0] == SQL_NULLABLE) ? SQL_NULL_DATA : SQL_NTS;
  if (!SQL_SUCCEEDED (SQLBindParameter (hStmt, 1, SQL_PARAM_INPUT, SQL_C_WCHAR, DataType[0], ParamSize[0], DecimalDigits[0], (SQLPOINTER) Empty, 0, &Empty_Length)))
    ODBC_Err (hODBC, "SQLBindParameter 1", DBC_Handle, hStmt);

  SQLRETURN RetCode = SQLExecute (hStmt);
  assert (RetCode != SQL_NEED_DATA);
  if (RetCode != SQL_NO_DATA && !SQL_SUCCEEDED (RetCode))
    ODBC_Err (hODBC, "SQLExecute", DBC_Handle, hStmt);
}



SQL Server Link server issue

$
0
0

I am trying to setup a linkserver between SQL Server 2014 EE and IBM DB2. I downloaded Ibm iSeries access for windows but IBMDA400, IBMDARLA, IBMDASQL providers are not being configured. Did anyone setup a link server between SQL Server and DB2 recently. Where can I get these providers?

Thanks in advance

not able onnect to SQL using anonymous login - not able to enable ' 'Anonymous..

$
0
0

Hi, I have a tool that access WMI locally or remotely fine except for 1 scenario when the wmi needs to access remote sql database (through Biztalk classes).

When SQL is installed on the same machine where I connect to wmi remotely, it works fine but when I connect to another machine that uses a remote sql server, it fails with the following error:

Internal error from OLEDB provider: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'."

After googling, I thought that I needed to change the account under which WMI service runs but it seemed as an impossible mission and is not recommended. Then I came across some articles indicating that I should enable "Network Access: Allow anonymous SID/Name translation" on the sql server machine following this MS article https://support.microsoft.com/en-us/help/839569/you-may-not-be-able-to-connect-to-an-instance-of-sql-server-by-using-a

My problem now is that when I run gpedit or secpol this "Network Access: Allow anonymous SID/Name translation" item is greyed out and cann't change anything.

So what are my options to be able to access sql in this case?

Thanks for your help

ADO Recordset AddNew/Update Identity Problem

$
0
0
Does anybody know what determines whether @@Identity or Scope_Identity() is used in the auto generated SQL sent to SQL Server by an ADO recordset Update method in classic ADO 2.8 with Client side cursor / Lock Optimistic, and with SQL Native Client 10 in the connection string.

The problem I have is that on my own development computer, I can see, using Profiler,  that SELECT SCOPE_IDENTITY() AS SCOPE_ID_COLUMN is part of the SQL generated by the Update - which is exacty what I want.

Yet, the same compiled program on a customer's server generats SELECT @@IDENTITY - which is bad news on a replicated database, as this means that the wrong ID is sometimes returned - due to the insert triggers used in SQL 2008 replication.

I've compared loaded DLL versions, assuming it must be due to the wrong/old dependency file related to data access, and I can't see anything abnormal here.

What is going on ?  How can I make the Recordet Update method always use Scope_Identity() ?

Linked Server issues using MSOLEDBSQL

$
0
0

I have configured Linked Server using MSOLEDBSQL provider and whenever i try to execute a select query involving Linked Server I get the below error:

Msg 8522, Level 16, State 3, Line 1
Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.


custom database occationally crashing - SQL backend, MS Access front end

$
0
0

We are running a custom database in one of my customer sites. The back end is running SQL and the front end is based on Microsoft Access. Our users occasionally experience issues with Access hanging on them and then they lose their reports. Other times, they experience sluggishness and with all these issues, we have not been able to narrow down why these issues happen.

Here is the technical stuff

SQL Server -> Windows 2012R2, 16GB ram, SQL version 2012, up to date windows updates. No additional AV running on this server.

Workstations -> new Lenovo M710s, Windows 10 Pro (v1903, OS build 18362.476), 8GB ram, SSD drives, Office 2016 Pro Plus, AVG business edition (19.7.3103)

HP Aruba Gbit managed switches (2530-24G-POE+)

               We are using POE because our phone system runs through the same connection.

Server backups run between 9am – 10am when there are the least number of users on the system using the database.

 

Things we’ve tried but didn’t make any difference

  1. Dropped in 3 new lines to the PC’s to take out the POE phones out of the equation.
  2. Removed AVG from a couple of stations for a few days.

 

I’m hoping that someone can give us some guidance on this issue.


I HAVE DEVELOPED A SOFTWARE USING EXCEL VBA IN WHICH I STORE DATA IN A SEPARATE ACCESS DB FILE AND I FETCH IT IN EXCEL AS PER MY NEED. BUT I AM UNABLE TO FETCH DATA USING WHERE CRITERIA IN SQL QUERY.

$
0
0

SQL = SQL & "WHERE [Purchase_date] <= textbox1.text"

purchase_date=field name in access

textbox1=a textbox in userform which contains date value

Bug report: ODBC Driver 17 for SQL Server fails to relay error messages containing apostrophes

$
0
0


Description: When SQL code or a SQL Server stored procedure raises a custom error message that contains an apostrophe, the error message is not relayed to the ODBC client application.

To replicate: Create a pass-through query in Microsoft Access, connected to a SQL Server 2016 database using ODBC Driver 17 for SQL Server. Use it to run a RAISERROR statement (or call any stored procedure that calls RAISERROR). Try an error message that does not contain an apostrophe vs. one that does.

RAISERROR ('Here is an error', 16, 1)

Produces the expected behavior: the error message is displayed. DBEngine.Errors(0) includes that error message.

RAISERROR ('Here''s an error', 16, 1)

Fails to display the error message. DBEngine.Errors(0) only contains 'ODBC--call failed'.

Impact: My front-end application validates user data entry through stored procedures that raise custom error messages and warnings as needed. Because of this bug, users can sometimes see why their data entry failed, and sometimes they only get the cryptic 'ODBC--call failed' error instead.

Drivers affected:

This problem was observed with ODBC Driver 17 for SQL Server version 2017.173.01.01 and version 2017.174.02.01

This problem did not occur when I raised the same error messages through the same front-end application, when the front-end application was connected to SQL Server using older ODBC drivers. Raising error messages that contain apostrophes works fine when running SQL or procedures in SQL Server Management Studio (Results pane displays the message correctly).

Persist Security Info

$
0
0

Hi,

Can someone explain to me the use of Persist Security Info = 'TRUE' on the SQL connection string from a DOT NET application. All microsoft documentation and best practices say that this should always be set to 'FALSE', but we have a publicly available Web application where the with SQL connections from the DOT NET applications installed on IIS. The SQL server itself has a CERT configured so I assume the connections are going to over a Secure channel.

So, should I set Persist Security Info = 'FALSE'? What are recomended practices? Why do we have Persist Security Info = 'TRUE' when it is recomended to keep it to 'FALSE'?

Thanks,

Venky

having issues with the agent job failure

$
0
0

Date12/2/2019 2:40:07 AM
LogJob History (DonorStudio - ETL Letters - Daily)

Step ID4
Server
Job NameDonorStudio - ETL Letters - Daily
Step Nameexec dbo.prcCheckTblKPDataFinal
Duration00:00:00
Sql Severity11
Sql Message ID50000
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0

Message
Executed as user: . Possible Bad data in tblKPDataFinal.  See prcCheckTblKPDataFinal [SQLSTATE 42000] (Error 50000).  The step failed.

This job failed to excute please what can i do to get it back running and what must have caused this issue 

SQL Server Agent is getting stopped after latest update

$
0
0

Dear Team,

After  latest  patch update on Windows server SQL server agent got stopped.It gives below error logs .

2019-12-03 10:24:59 - ? [100] Microsoft SQLServerAgent version 11.0.5058.0 (X64 unicode retail build) : Process ID 8284
2019-12-03 10:24:59 - ? [495] The SQL Server Agent startup service account is NT SERVICE\SQLAgent$SP2013.
2019-12-03 10:24:59 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2019-12-03 10:25:29 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2019-12-03 10:25:59 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2019-12-03 10:26:29 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2019-12-03 10:26:59 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2019-12-03 10:26:59 - ! [000] Unable to connect to server 'SHAREPOINTDB\SP2013'; SQLServerAgent cannot start
2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
2019-12-03 10:26:59 - ! [165] ODBC Error: 0, Data source name not found and no default driver specified [SQLSTATE IM002] 
2019-12-03 10:26:59 - ! [382] Logon to server 'SHAREPOINTDB\SP2013' failed (DisableAgentXPs)
2019-12-03 10:26:59 - ? [098] SQLServerAgent terminated (normally)

Kindly suggest how to overcome this problem. If it not get resolved we will revert the patches on Production.

Regards,

Shushant

MSOLEDBSQL Provider. Error using ADODB.Command XSL property

$
0
0

Hi,
First post so apologies if I break any forum rules.

We are undertaking a migration from SQL20082 to SQL2017 on Windows 2016. The new Windows 2016 servers are secured to use TLS1.2 only and therefore our legacy applications that use ADO are being updated to use the new MSOLEDBSQL provider instead of SQLOLEDB.

I am comfortable with the changes to all the connection strings and am aware of the requirement to include DataTypeCompatibility=80 to match data types.

Generally speaking the migration is progressing well, however one application has thrown up an error when attempting to assign a value to the XSL item in the ADODB.Command.Properties collection. An excerpt from the code appears below.


  Set cm = New ADODB.Command
  Set cm.ActiveConnection = 'my ADODB.Connection object'
  Set cm.CommandStream = 'my String'

  cm.Properties("xsl") = 'path to XSL file

Error 3265 occurs when attempting to assign the XSL value. It would appear this property item does not exist when using the MSOLEDBSQL provider. I have been unable to find a solution on the net so far and was wondering if anyone else has encountered this issue and knows of a workaround, short of recoding.

Thanks in advance



Win 10 client can't connect

$
0
0

Hi all,

I have a client app which I have been installing on various computers that run Win 7 in a domain. This has worked fine. I installed this same app on two Win 10 computers and I get the following message:

"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections."

Since the database login credentials are hard coded, and has worked on every installation (with Win 7) I can discard all of the possible options above except the "not accessible".

Tech support for the org just got back to me. They disabled the anti virus and the firewall and this had no effect.

I am researching this further; however, I wanted to ask here whether anyone has had this issue come up and if so, what steps I can take to resolve it. Since I built the app using VS2015 on a Win 7 PC, I wonder if it will make a difference if I re build it on a PC with VS2015 and Win 10. (We are entering the piñata stage!) Thank you for your time and assistance.

Update: Spelunking I found that this database is hosted on an SQL Server 2000. Could this an issue with Win 10?

Saga

PS: I wasn't sure if this was the correct group. Feel free to move to post if necessary.


You can't take the sky from me


Views not returning complete data

$
0
0

I recently started a factory position that uses SQL to store machine data. One of the Views in a database is set-up to return values for about 10 different columns. The problem is that the Views query only returns a very small portion of results from the past year. Why am I only getting a few results out of many thousands?

I apologize in advance for the lack of technical expertise. I'm literally the only person in my facility who is responsible for all of this, and I'm new. 

SQL server to DB2 database federation

$
0
0

I am new to SQL Server. 

I have a Sql server 2016 database and db2 luw 10.5 database.

I want to access the db2 tables as remote views within my sql server database without replication.

This I know with other database can be achieved via heterogeneous federation.

I wanted to know if the same exist with Sql server and if some one can send me a link to some documentation on how to set this up.

thank you

Laxmi

Dynamic Database SSRS URL Access error

$
0
0

Hey all,

While trying to export a report as a PDF using URL Access, I ran in to a problem.
I'm trying to use a dynamic database/datasource for the data for this report. 

I've set up a dynamic datasource according to the SSRS documentation, but this does not work. 
Using Report/&DatabaseName=<Database I want to use>&ServerName=<Server>&rs:Format=PDFas the parameters in the URL I always get this error: Cannot create a connection to data source 'Dynamic_DB'. (rsErrorOpeningConnection). 

Is there a way that I can see more information about the error to see exactly what is going wrong or is there a direct way to fix this issue?

I'm using SQL Server 2017.

Kind Regards,
Devinloper

New ADODB from Win 10 (1803) too slow

$
0
0

Hello

Some time ago I updated my Windows 10 Pro to 1803 build.

Today I detected than my tests, created on VBScript and ADODB work very slow.

For compare

1. At computer (Intel 2670QM) with Win7 (msado15.dll 6.1.7601.24023, cscript.exe 5.8.9600.19003) my tests execute within 80 sec.

2. At computer (Intel 6950X) with Win10 1803 (msado15.dll 10.0.17134.1, vbscript.dll 5.812.10240.16384) my tests execute within 1080 sec.

Windows.old (at computer with Win10) contains:
 - vbscript.dll - 5.812.10240.16384
 - msado15.dll - 10.0.16299.248

Early (before update to build 1803) my tests worked as expected - very fast (~80 sec)

The problem locates in cycle:

 for i=1 to c_recordN cmd(0)=base_ID+i call cmd.execute()
 next 'i

Where "cmd" it is "ADODB.Command" object.

I not sure, but seem the problem in "Execute" method.

Where I may find the informations about changes in new msado15.dll 10.0.17134.1?

Thanks,

Dmitry Kovalenko

www.ibprovider.com

Viewing all 4164 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>