Forum Discussion
ADO & VARCHAR
Aha - found other postings with the same issue, and someone posted a workaround (which seems to be working for us). I think it still a bug and a serious regression, but at least we can move forward (we happen to be at a point in the product cycle where we can put in a change like this)
https://stackoverflow.com/questions/52650021/msdatashape-error-broken-on-upgrade-to-windows-10-feature-update-1809
* workaround for this issue ... Replacing adVarChar(##) with adLongVarChar does the job for me ...This workaround is not applicable to queries like
SHAPE APPEND NEW adLongVarChar As INVNO, NEW adLongVarChar As iCP,
((SHAPE APPEND NEW aadLongVarChar As INVNO,NEW adLongVarCharAs iCP,NEW adLongVarChar As F1,NEW adLongVarChar As F2,NEW adLongVarChar As F3)
AS Trans RELATE INVNO TO INVNO,iCP TO iCP)* someone else suggested using adLongVarWChar
* there was also mention of a future deprecation of the Data Shaping Service for OLE DB
https://docs.microsoft.com/en-us/sql/ado/guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider
Any updates on this? I can't believe we are the only ones having this problem. Is Microsoft monitoring this forum, and if not, where is the correct place to report problems with Windows Server 2019 Preview?