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

11015 - '[qodbc]

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

  • 11015 - '[qodbc]

    Al and others I'm working with a copy of the SalesOrderLine table and setup an active link to update Quickbooks.

    I need to update one of my custom fields on many records, however when doing so I'm getting the following error when trying to update the CustFldSalesOrderLnCategory1.

    11015 - '[QODBC] Expected lexical element not found:
    SQL state is: 42000'
    refresh the data to see the current server values.

    After researching QODBC website the solution provide are not working anyone else run into this problem?

    I've limited the table to just two fields using the following statement. I've also tried a few different statements with no results. Any help would be great.

    WHERE FQPrimaryKey = :old.FQPRIMARYKEY
    AND (CustFldSalesOrderLnCategory1 = :old.CUSTFLDSALESORDERLNCATEGORY1 OR CustFldSalesOrderLnCategory1 IS NULL AND :old.CUSTFLDSALESORDERLNCATEGORY1 IS NULL)​​​​​​


    Thanks
    John

  • #2
    For testing work with connecting via vdemo to get the SQL right. That'll cut down the layers you are going through.

    It's the old divide and conquer.
    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
      Originally posted by Al Buchholz View Post
      For testing work with connecting via vdemo to get the SQL right. That'll cut down the layers you are going through.

      It's the old divide and conquer.
      Forgot about that one :)

      Comment


      • #4
        Originally posted by jtm311 View Post

        Forgot about that one :)
        Al thanks it helped to get to the next problem :) I now see after correcting the statement the field is can not be updated. Any way around this or make a change in QB? Thanks
        QB_table.JPG

        Comment


        • #5
          Originally posted by jtm311 View Post

          Al thanks it helped to get to the next problem :) I now see after correcting the statement the field is can not be updated. Any way around this or make a change in QB? Thanks
          QB_table.JPG
          Probably need to make a change at a detail level that sums into that bill due field...

          ie add a credit or debit to change what is due.
          (Bad horizontal tracking on my part. Found the wrong fieldname... corrected by adjusting my glasses...)
          Last edited by Al Buchholz; 07-12-2020, 10:01 AM.
          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


          • #6
            Al sorry I'm working with the Category 1 field and it shows it won't allow updates from external. Unless I missed your point. Thanks

            Comment


            • #7
              Originally posted by jtm311 View Post
              Al sorry I'm working with the Category 1 field and it shows it won't allow updates from external. Unless I missed your point. Thanks
              Oops. Looks like you're stuck. I haven't tried to write to a custom field.
              You need to handle that field differently or use some other option.
              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


              • #8
                Originally posted by Al Buchholz View Post

                Oops. Looks like you're stuck. I haven't tried to write to a custom field.
                You need to handle that field differently or use some other option.
                Thanks for the effort... VB helped get me this far.

                Comment

                Working...
                X