You are viewing limited content. For full access, please sign in.

Question

Question

ODBC Connection - Workflow - Error retrieving data when using letters

asked on June 1, 2015

When I Query Data within a Workflow, if I only use numbers, it returns rows. However, if the search includes letters, I get a "Data Type Mismatch in Criteria Expression" error. Has anyone run into this or have a solution? It's a CSV file, not a SQL database so I do not have specific data type declared.

0 0

Replies

replied on June 1, 2015

Your VAR has opened a case for this issue. We've asked him to confirm the configuration so that we can arrive at a resolution.

1 0
replied on June 1, 2015

Thank you. I just figured I'd ask to see if anyone else had the issue.

0 0
replied on June 1, 2015 Show version history

No worries. We have not heard back from your VAR.  Can you make sure that you have the correct configuration for ODBC.  According to your VAR, you have a 64 bit OS with 64 bit Workflow.  You will need to check the client machine where the CSV is located and make sure that your ODBC drivers match the configuration of the server.
You can refer to the configuration here.   Further background information can be found here.

0 0
replied on June 2, 2015

I have installed the Access 2010 distributable like it says in the Workflow Help.

They called me yesterday and took down all my software versions. I am running 64bit Windows Server and Workflow Designer.

What am I looking for on the remote machine to make sure it matches? Will I need to install the 2010 on both?

0 0
replied on June 2, 2015

I have verified I did install the 64-bit Access 2010. It is now on both servers (the Workflow server and the Server with the CSV file) and still does not work. I understand my VAR has made contact.

0 0
replied on June 2, 2015

Yes, thank you. We are asking him for a copy of the workflow WFI file, the query and the CSV you use.  We will be in touch through your VAR.

0 0
replied on June 3, 2015

For the benefit of other readers, the ODBC data type for the field was an integer field.  Setting it to LongChar resolved the issue.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.