OLE DB Services can be used with Ora OLEDB through C /COM or ADO.
By default, the For C /COM applications, some additional steps are needed to use OLE DB Services.
Referencing both libraries is likely to generate an ambiguous object error.
To avoid this type of error, give priority to the library that your code references the most.
Marty With DAO you can also open a recordset on a table in an external database without linking it - either use Open Database to create a Database object, then Open Recordset to open a recordset in that database, or specify the external database in the SQL for the recordset.
I thought with ADODB I could connect to the table and make the changes without linking to the FE. I've used DAO in the past for similar functions, but I would link it in with an alias name which requires additional housekeeping to manage the alias which I was trying to avoid.
The following code snippet shows one way that C /COM applications can enable OLE DB Services.
The code shows the OLE DB consumer creating an instance of the , NULL, CLSCTX_INPROC_SERVER, IID_IData Initialize, (void**)&p IData Initialize); // Set properties, datasource name, userid, and password, etc. // Create an OLEDB data source object using the interface obtained from the // CLSID_MSDAINITIALIZE class.As an Access developer — or even as a power user — you won't get far if you can't work with the Recordset object.But it's easy to go astray, and there are a number of mistakes that even experts make. Often, we're unaware of a subtle nuance between the two object libraries, Data Access Objects (DAO) and Active X Data Objects (ADO).function to create an instance of the data source object.This function requires important information about the provider: class ID of the provider and executable context. [quote name='Andrew KKWalker' post='799729' date='24-Oct-2009 ']There must be more code involved than this, because I cannot see the logic behind this.