Looks like we can just as well use ADORecordset here
...instead of _ADORecordset, to make this consistent with the reset of the ADO driver code. (Appears the former is a #define for the latter.) Change-Id: I0b2d89e4483cf7f441df2cf2ceef7bfd37866cf9
This commit is contained in:
@@ -104,7 +104,7 @@ bool WpADOConnection::Execute(const OUString& CommandText,OLEVariant& RecordsAff
|
|||||||
{
|
{
|
||||||
assert(pInterface);
|
assert(pInterface);
|
||||||
OLEString sStr1(CommandText);
|
OLEString sStr1(CommandText);
|
||||||
bool bErg = SUCCEEDED(pInterface->Execute(sStr1.asBSTR(),&RecordsAffected,Options,reinterpret_cast<_ADORecordset**>(ppiRset)));
|
bool bErg = SUCCEEDED(pInterface->Execute(sStr1.asBSTR(),&RecordsAffected,Options,reinterpret_cast<ADORecordset**>(ppiRset)));
|
||||||
return bErg;
|
return bErg;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user