Spoiler alert! Since I can only write this entire book basically the same for each OLEDB Provider and have 3 for 32-bit and 4 in 64-bit, I must apologize in advance for the use of the same book but with the code changes based on the chosen Provider. Please do not buy this book if it says VS2022,VB.Net, SQL Server, ADO AND RDL Reports. Instead, please replace the connection strings used in the book you purchased and replace them with what I’m using in this book.
For Windows Authentication:
"Provider= SQLNCLI11; Data Source=WIN-U1D8NGFVABF; Integrated Security=SSPI;Initial Catalog=AdventureWorks2019;"
There also is an entire website devoted to connection strings. It is:https://www.connectionstrings.com
I wish you the best of luck in your future learning of how to use OLEDB Providers to create RDL Reports.
I have no idea why that is. I heard about it happening in fiction work. I never expected to see it happen in the world on non-fiction. Never-the-less, this book has pretty much done that, and I think I like what I am seeing so far. But before I go further, welcome to my world of lions, tigers, and bears. Replace them with Providers, Drivers and ISAMs and you’re in my jungle. I have 20 ISAMs, 14 Drivers and tons of Providers that need to be - in their own right - a standalone book of their own. Will you let me do that? Or will you write a cranky review with key words: Rehash, Found on the Web, Don’t waste your time, and last but not least: Not worth the paper it was written on. Ha, ha, ha. Until you need it. I handled 3000 cases while working for Microsoft in technical support for the Enterprise version of Visual Basic. Close to 50 percent of the $90 calls involved Database related issues and almost half of those were about getting the connection string right. It is my intent to write about what I know works and that includes using Reports as the end product. I will take you from beginning to end.