Power Platform Community Forum Thread Details

Power Automate Desktop worked very well with Access 2016. For example, I ran CREATE TABLE, DROP TABLE, and ALTER TABLE queries from PAD in the Access 2016 database without any issues.

We switched to Access 2021, and SELECT queries initiated from PAD continue to work on OLD TABLES created in Access 2016. However, SELECT queries initiated from PAD no longer work on NEW TABLES created in Access 2021 (error message: database engine cannot find the input table or query '09TEST'), even though this same SELECT query works in Access on these new tables.

An additional interesting point is that the CREATE TABLE command initiated from PAD runs through, but the created table is not visible in Access. However, the table does exists because running the CREATE TABLE query again from PAD returns an error indicating that the table already exists (Error in SQL statement '09TABLE2' already exists).

I am grateful for any help; I spent an entire afternoon on this problem. Here is the detailed error message for the SELECT query initiated from PAD on the new table created in Access 2021:

Correlation Id: c31fc392-261f-443d-b355-4a44dbf1bdcf

The Microsoft Access database engine cannot find the input table or query '09TEST'. Make sure it exists and that its name is spelled correctly.: Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.ActionException: Error in SQL statement The Microsoft Access database engine cannot find the input table or query '09TEST'. Make sure it exists and that its name is spelled correctly. ---> System.Data.OleDb.OleDbException: The Microsoft Access database engine cannot find the input table or query '09TEST'. Make sure it exists and that its name is spelled correctly.

at System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(OleDbHResult hr)

at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult)

at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)

at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

at System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior)

at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)

at Microsoft.Flow.RPA.Desktop.Modules.Database.Actions.DatabaseActions.ExecuteSQLStatement(Variant connectionString, Variant sqlConnectionVariable, Variant sqlCommand, Variant& result, Int32 timeout, Int32 getConnection)

--- End of inner exception stack trace ---

at Microsoft.Flow.RPA.Desktop.Modules.Database.Actions.ExecuteSqlStatement.Execute(ActionContext context)

at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)

Categories:

Power Automate Desktop