From dca94d10c857b6fcbcf3d4fd85fa4b98fc7ec583 Mon Sep 17 00:00:00 2001
From: Stephan Bergmann <sbergman@redhat.com>
Date: Tue, 19 Sep 2017 09:32:23 +0200
Subject: [PATCH] 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
---
 connectivity/source/drivers/ado/Awrapado.cxx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/connectivity/source/drivers/ado/Awrapado.cxx b/connectivity/source/drivers/ado/Awrapado.cxx
index 75d1b6a3ae11..4a71534c01fb 100644
--- a/connectivity/source/drivers/ado/Awrapado.cxx
+++ b/connectivity/source/drivers/ado/Awrapado.cxx
@@ -104,7 +104,7 @@ bool WpADOConnection::Execute(const OUString& CommandText,OLEVariant& RecordsAff
 {
     assert(pInterface);
     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;
 }