Tags » Oledb

DBConnectTester - Demo .NET app for connection string testing

(Updated 10/23/2016)

Level: Beginner

Source Code: https://github.com/vbp-ph/DbConnectTester

Programming Language: VB.NET (2010)

Required Skills: basic understanding of .NET libraries, Sub Procedures

Purpose: Test connection strings

Additional Packages: 72 more words

.NET

The Microsoft.Jet.OLEDB.4.0 - Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine

Khi sử dụng OLEDB gặp lỗi sau:

The Microsoft.Jet.OLEDB.4.0 hoặc Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine.

Nguyên nhân lỗi là do máy tính hiện tại đang sử dụng Offices 32 bit nhưng mặc định biên dịch của Visual Studio là Any CPU. 81 more words

.NET

Setup a Linked Server to MS Access from SQL Server - Beat the errors

Normally, it is easy enough to setup a Linked Server on SQL Server to other data sources. Problems are usually caused by one of the usual culprits that have to be addressed… 731 more words

SQL Server

Using appRules to Read and Process Stored Procedure Records

appRules Studio includes workflow activites for reading records from a stored procedure.  By utilizing the stored procedure related activities, the stored procedure records and the fields they contain can be read from the database and utilized in appRules just like any other records and fields. 393 more words

Databases

Oracle, Passwords and SSIS Packages

I have spent the last two weeks banging my head on why I couldn’t get Oracle password to save in the SSIS package despite using the config file or decrypt and a multitude of other options.   234 more words

Technology

'OraOLEDB.Oracle.1' is not registered on local machine

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/95d8e522-75b6-4ee3-a691-d2e76b25d56a/oraoledboracle1-is-not-registered-on-local-machine?forum=sqlintegrationservices

I nearly pulled my hair out finding the solution to this problem.

In the end I installed “32-bit Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studio” on my 64 bit system, and it solved the problem. 27 more words

SSIS