Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Invalid Precision Error HY104

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Invalid Precision Error HY104

    Hi,

    I am a DBA and have a developer using Alpha5 v10.5. He is writing to MSSQL v2005 table. We have a DEV and Production environment setup and he is carrying out exactly the same steps in both which is to insert text to a field which is defined as VARCHAR(MAX). The error he recieves is as follows in the PROD environment but not in DEV:

    Record was not inserted:
    Database API specific error [Microsoft][ODBC SQL Server Driver]Invalid precision value SQL State is: HY104

    I have attached a screenshot of the error also. I have googled many forums and understand this is the ODBC API error but I can't find a fix. It is even more fustrating as it works in DEV but not in PROD.

  • #2
    Re: Invalid Precision Error HY104

    I'm getting the same error today on an nvarchar(max) SQL field. Did you ever figure this out?

    Comment


    • #3
      Re: Invalid Precision Error HY104

      Hi Iviowa,

      unfortunately not, the problem still exists after trawling through so many different forums I am none the wiser, if you find a solution I would appreciate you letting me know.

      Comment


      • #4
        Re: Invalid Precision Error HY104

        DEV and PROD have same Alpha build?
        What version number. Why use odbc if there is a native connect.

        Comment


        • #5
          Re: Invalid Precision Error HY104

          Hello
          try to disable write conflict flag.

          Marco
          Marco Kregar

          From the north of Italy, here ....

          Comment


          • #6
            Re: Invalid Precision Error HY104

            Both DEV and PROD are on the same (latest build). We are using native connect, but the error mentions ODBC? Disabling the write conflict flag unfortunately does not resolve the problem.

            Replying on behalf of batsy.

            Regards

            Comment


            • #7
              Re: Invalid Precision Error HY104

              Both DEV and Prod are running the same version (2972_3566). It's not the very latest version by I tried updating the lastest (3040_3571) but still go the error. Then went back to earlier version.

              The "Check for write conflicts" is unchecked.

              I'm not using ODBC. I'm using AlphaDAO. The radio button that is checked for Data Source is: "Remote Database accessed via AlphaDAO (Alpha Data Access Object)". I don't know why the error says "ODBC".
              Last edited by iviowa; 08-05-2010, 09:59 AM. Reason: typo

              Comment


              • #8
                Re: Invalid Precision Error HY104

                Here is my solution for now. If anyone has a better idea, please let me know.

                If I change my connection string to SQL 2000 it works:
                {A5API='SQLServer',A5DBVersion=2000,Server='ServerName',A5ANSINullPadWarn=Default,Trusted_connection=yes,Database='DatabaseName'}

                I only changed the components that were getting an error saving to an nvarchar(max) field. All other components still use 2008. I tried 2005 but got the same error:
                {A5API='SQLServer',A5DBVersion=2008,Server='ServerName',A5ANSINullPadWarn=Default,Trusted_connection=yes,Database='DatabaseName'}

                BEWARE: This will not work if you are using ‘Date’ fields. ‘Date’ fields (date portion only – no time part) were introduced in SQL Server 2008

                Once you make the change you will need to publish the new connection string to the server. Remember to add the connection string to the “Named AlphaDAO connection strings” in your publish settings. Republish checking “All files in the project”, uncheck “Publish new or modified files only”, click “Clear Publishing History”. I also had to restart the Application Server for the connection string to be available.

                Alpha Software worked a great deal with me to try to recreate the problem but together could not recreate it. For what it's worth, my thinking is that it may be more of a Microsoft SQL driver issue than an Alpha Software issue.

                Comment


                • #9
                  Re: Invalid Precision Error HY104

                  I was having this same issue, and changing the server in my connection string from 2008 to 2000 fixed it, but I didn't like the fact of being limited to using data types that were 2000 compliant. Below is a description of the cause of this problem, along with a fix.


                  Using a version of 2008 tells Alpha Five that you intend to work with SQL Server 2008 or 2008R2 or above and will be using the 2008 version of the native client for SQL server. A mismatch in the client driver can cause the error you are seeing. If you haven’t already, download sqlncli.msi for X86 on each client accessing your SQL Server database.

                  http://www.microsoft.com/download/en....aspx?id=16978


                  Microsoft® SQL Server® 2008 R2 Native Client
                  Microsoft SQL Server 2008 R2 Native Client (SQL Server Native Client) is a single dynamic-link library (DLL) containing both the SQL OLE DB provider and SQL ODBC driver. It contains run-time support for applications using native-code APIs (ODBC, OLE DB and ADO) to connect to Microsoft SQL Server 2000, 2005, or 2008. SQL Server Native Client should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2008 R2 features. This redistributable installer for SQL Server Native Client installs the client components needed during run time to take advantage of new SQL Server 2008 R2 features, and optionally installs the header files needed to develop an application that uses the SQL Server Native Client API.

                  Audience(s): Customer, Partner, Developer
                  X86 Package (sqlncli.msi)
                  X64 Package (sqlncli.msi)
                  IA64 Package (sqlncli.msi)

                  Comment


                  • #10
                    Re: Invalid Precision Error HY104

                    The 11-30-2011 04:17 PM solution above solves the problem for the Application Server v11.

                    Comment


                    • #11
                      Re: Invalid Precision Error HY104

                      Originally posted by lsprowls View Post
                      The 11-30-2011 04:17 PM solution above solves the problem for the Application Server v11.
                      a link would be nice.

                      I've seen you build one before, so you know how to do it..

                      Or are you referring to post #9 of this thread?

                      I'm guessing that you are on US eastern time. There are ~ 23 other time zones that show a different time for that post......
                      Last edited by Al Buchholz; 01-12-2012, 09:37 PM.
                      Al Buchholz
                      Bookwood Systems, LTD
                      Weekly QReportBuilder Webinars Thursday 1 pm CST

                      Occam's Razor - KISS
                      Normalize till it hurts - De-normalize till it works.
                      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                      When we triage a problem it is much easier to read sample systems than to read a mind.
                      "Make it as simple as possible, but not simpler."
                      Albert Einstein

                      Comment


                      • #12
                        Re: Invalid Precision Error HY104

                        Yes, the answer is to download and install a Microsoft SQL Server 2008 R2 Native Client linked in Post #9.

                        Comment


                        • #13
                          Re: Invalid Precision Error HY104

                          It is working, make sure to install this on your sever running the alpha five server
                          Last edited by Islip; 03-01-2012, 05:24 PM.

                          Comment


                          • #14
                            Re: Invalid Precision Error HY104

                            What about SQL Server 2012 Business Intelligence? I'm getting the error when I try to update an image field.

                            Both the App and Dev are same version. I can insert the image when running the preview from the Dev, but once published, it doesn't work.
                            Last edited by dfricke10; 12-20-2012, 04:50 PM.

                            Comment


                            • #15
                              Re: Invalid Precision Error HY104

                              Nevermind. Got it. Since upgrading to SQL 2012, I never changed the connection string to 2012 instead of 2008. I also installed the Microsoft SQL Server 2012 Native Client from here http://www.microsoft.com/en-us/downl....aspx?id=29065 before doing that, so I really don't know which one fixed it. But it works now.

                              Comment

                              Working...
                              X