I have a query regarding a specific Property “Add Headers” which is present in reading Excel/workbook activities. When this option is unchecked, Excel introduces arbitrary column headers and treats the actual headers as regular rows.
I am interested in understanding how a similar outcome can be achieved in the context of using Excel as a database.
I’vee checked by adding HDR=No to my connection string but it didn’t work for me
Could you provide us with the attempted connection strings, so that we can avoid suggesting you with the same again.
Also, Have you checked the below Blog :
Connection strings for Excel. Connect using CData ADO.NET Provider for Excel, Microsoft.ACE.OLEDB.12.0, Microsoft.Jet.OLEDB.4.0, OleDbConnection.
Below is my Connection String
To aid in understanding, I’ve added a screenshot here below
Did u check with this tutorials on this
How to connect with Excel as a database ?
Perform the details mentioned in the Step by step guide, for connecting Excel as a database
Open Excel file (Note - Excel file must remain open)
In UiPath Studio Drag and drop Connect / Execute (Non) query activity
Click Configure connection
Open Connection Wizard
Select Microsoft ODBC Data Source
Use Connection String
Go to Machine Data Source
Microsoft Excel Driver(.xls)
Give Some Data Source Name and Desc…
Yes i have checked the tutorials but am not able to access the xaml file nor the spreadsheet
I get the below message when i try to login
Yeah I think it’s not public
Well anyhow this topic was split into another video tutorial
In order to connect dynamically to Excel from UiPath I suggest you use OLEDB. Then you will be able to use mysql to retrieve data from the Excel into a data table.
Here is a YouTube video how you can do it:
[UiPath: Manipulate Excel with SQL]
Thanks for your PM
in general, we would assume: Pseudo column names (A,B,C) are used instead
Its good to cross-check it within a RnD to get it validated and we encourage you to do so.
When the RnD is not working as expected then let us know all details:
Studio Version, relevant Package versions, set Project Compatibility
Data Source / Provider / ODBC Details
Maybe a side test by crosschecking with a SQL Client can help also