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

Question

Question

ERROR [HY104] [Microsoft] [ODBC Microsoft Access Driver] Invalid precision value

asked on December 14, 2015

I am having an issue with workflow Version 9.2.1.227 writing back to an Access database. I am currently using the database Access 97-2003 format. The ODBC seems to link fine but the error message I get is this: (btw I can make it work with an Excel Sheet)

ERROR [HY104] [Microsoft] [ODBC Microsoft Access Driver] Invalid precision value

I believe all the fields allow for the correct number of characters and the types of fields are all text except the date field saving into the date field. I am assuming the invalid precision value is referring to data not being able to be stored, but not sure what it could be.

 

0 0

Replies

replied on December 14, 2015

After messing around a little I found a post somewhere on this site that said the old memo or new long text field could be a problem. I changed the one field that was using this to short text and limited the text to 255 characters. Now the error message has changed to:

ERROR [42000] [Microsoft][ODBC Microsoft Access Driver] Syntax error in INSERT INTO statement

I am simply using the "Insert Data" tool in workflow, so I am not writing my own statement!

0 0
replied on December 15, 2015

In the meantime I have also tried to alternately connect using OLEDB. When I try that, it will not even let me build out the connection erroring out with 

File Browsing not enabled on server.

I have also locally installed Access on the workflow server to see if that may solve the problem and it did not.

 

0 0
replied on December 15, 2015

For the first error, it sounds like the numbers you were trying to insert exceed the precision specified for the column in Access (either too many decimals or too many digits).

One of the reasons the syntax error could happen is because the Access driver does not support columns with spaces in their names. Do your columns have spaces in their names?

I'm not sure if installing Access installs the OLEDB driver. You can turn on file browsing on the WF Server from the  WF Admin Console under Server Configuration\Security.

0 0
replied on December 17, 2018

Hello Miruna or Ingeborg,

I am having the same error. Will you please elaborate on where to turn on file browsing? My WF Admin Console has "Server Configuration" but not "Security".

Thanks,

Julie

0 0
replied on December 17, 2018

Actually nevermind ... I figured out a workaround.

Thx,

Julie

0 0
replied on December 15, 2015

None of my columns have spaces and there is no issue with numbers and decimals because I am only using text fields and one date field. It is what I thought the issue was as well.

One of the guys at my VAR MCCI showed me where to turn the file browsing on and now I was able to make an OLEDB connection with NO errors whatsoever. It must be the ODBC driver. Frankly, if it will work with OLEDB then I will forego trying to fix this with ODBC.

Thanks 

Inky

0 0
replied on December 15, 2015

Is that the ODBC driver from Microsoft Access Database Engine? What version is it?

0 0
replied on June 10, 2022

Hello
we are having the same problem, is there any solution you can share?

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

Sign in to reply to this post.