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

Help on API specific error!!

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

  • Help on API specific error!!

    Hi all, I have a problem on creating a passive link table through QODBC. The Error message is as below:

    Database API specific Error
    11012 - [QODBC] Assignment Error
    SQL state is 22018 while converting resultset to DBF table

    I have WIN7 OS, A5V10, QB Premier manufacturing and wholesale edition.

    Interesting things are there is no problem when I use other computers (with WIN XP, VISTA) and the QB table I tried to get is "purchaseorderline" and that is the field "PurchaseOrderLineRate" causing this problems, other fields in this table are alright.

    Any advice is appreciated.
    Last edited by xiangshu; 08-31-2010, 05:06 PM.

  • #2
    Re: Help on API specific error!!

    Not sure I've seen that before.

    Searched for the error and found a reference to a field have too large of a value in it.

    Did you try the exact same QB company file on another computer and did that work?

    I'd suggest that you go to QODBC.COM and download the latest QODBC driver and install it. Skip the trial/license info and run QRB again.
    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


    • #3
      Re: Help on API specific error!!

      Thanks you for the reply Al. I've tried on other computers with XP and VISTA though. It works perfectly. I kind of visually checked the "rate" in the table, NO HUGE NUMBER.Besides, the A5 picked the value as "exponent numeric" and the "amount" value should be larger. Does this link to some QODBC'S settings?

      Can you please explain "found a reference to a field have too large of a value in it"? This is the meaning of 11012 or 22018?
      Last edited by xiangshu; 08-31-2010, 05:53 PM.

      Comment


      • #4
        Re: Help on API specific error!!

        Originally posted by xiangshu View Post
        Thanks you for the reply Al. I've tried on other computers with XP and VISTA though. It works perfectly. I kind of visually checked the "rate" in the table, NO HUGE NUMBER.Besides, the A5 picked the value as "exponent numeric" and the "amount" value should be larger. Does this link to some QODBC'S settings?

        Can you please explain "found a reference to a field have too large of a value in it"? This is the meaning of 11012 or 22018?
        qodbc website found by a google site search ie site:qodbc.com 11012

        probably a mismatch of the qb field size and the target field size

        post your SQL statement
        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


        • #5
          Re: Help on API specific error!!

          Sorry Al, Could you please tell me where to get this SQL statment?
          My action was simple: In A5, new table->passivelink table->create a single passivelink table->create ad hoc datasource-> ad hoc connection string, build and then select from table column and finish.

          I 've checked VB demo, everything is fine by using that.
          Do you think this is related to some A5 settings?

          Comment


          • #6
            Re: Help on API specific error!!

            Originally posted by xiangshu View Post
            Sorry Al, Could you please tell me where to get this SQL statment?
            My action was simple: In A5, new table->passivelink table->create a single passivelink table->create ad hoc datasource-> ad hoc connection string, build and then select from table column and finish.

            I 've checked VB demo, everything is fine by using that.
            Do you think this is related to some A5 settings?
            Join the webinar today and we'll work this
            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

            Working...
            X