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

QBKS 2021 Enterprise, refreshing passive link table

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

    QBKS 2021 Enterprise, refreshing passive link table

    I set up a db In A5 V12.3, build 2689, to connect to Quickbooks Enterprise back in 2017, version 2017, every year I upgrade and download the new QODBC, and not many problems ,this year 2021 I cannot seem to figure out where my problem is.
    I get this error message Screenshot 2021-08-24 16.08.26.png

    I have went through each of the passive link tables and they all connect but don't understand the error message and it does not update the tables.
    any Idea where to look?
    Thanks
    David
    A5V12.3
    Win7, 64 bit
    Qbks 2018 Enterprise
    QODBC R/W

    #2
    here is what the Trace windows shows:
    Code:
    addin.variables().a5_error_show(Script:OnPush line:38
    pr =a5_RefreshPassiveLinkTable(table_i,.f.,.f.)
    Result set row requested not found while getting result set data column 1.) : Property not found
    *INTERMEDIATE_0000004f.a5_error_show method not found.
    I don't know what has changed except upgrading Quickbooks from 2020 to 2021
    then I installed the newest QODBC for 2021
    David
    A5V12.3
    Win7, 64 bit
    Qbks 2018 Enterprise
    QODBC R/W

    Comment


      #3
      I think it is in my "Where clause"

      ( IsManuallyClosed = 0 ) AND
      ( IsFullyInvoiced = 0 ) AND
      ( SalesOrderLineIsManuallyClosed = 0 )

      when I add this last line, I get an error:

      ( Salesorderlinequantity - Salesorderlineinvoiced) > 0

      this last line is what was in the previous version 20,


      Screenshot 2021-08-25 13.35.38.png

      Screenshot 2021-08-25 13.39.30.png
      Attached Files
      David
      A5V12.3
      Win7, 64 bit
      Qbks 2018 Enterprise
      QODBC R/W

      Comment


        #4
        that got rid of the Where clause error in the picture above.
        I had recreated the the passive link table and it works until I add the last line :
        ( Salesorderlinequantity - Salesorderlineinvoiced) > 0
        now when I refresh the table it never finishes



        Screenshot 2021-08-25 14.19.23.png I left out an "AND" before the last line.

        David
        A5V12.3
        Win7, 64 bit
        Qbks 2018 Enterprise
        QODBC R/W

        Comment


          #5
          Glad you got it resolved David.
          I tend to use a different type of SQL builder. My preseference is TOAD for SQLServer, but there are many others.
          Constructing a script in these will give more insight into anything incomplete or incorrect.
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment


            #6
            in summary this is what worked for years on a daily basis several times a day:
            Code:
            IsManuallyClosed = 0 AND IsFullyInvoiced = 0 AND SalesOrderLineIsManuallyClosed = 0 AND (Salesorderlinequantity - Salesorderlineinvoiced) > 0
            the only change was upgrading from QBKS 2020 enterprise to 2021 and uprade the QODBC

            Now I removed
            Code:
            AND (Salesorderlinequantity - Salesorderlineinvoiced) > 0
            and it works perfect.
            David
            A5V12.3
            Win7, 64 bit
            Qbks 2018 Enterprise
            QODBC R/W

            Comment


              #7
              Originally posted by David View Post
              in summary this is what worked for years on a daily basis several times a day:
              Code:
              IsManuallyClosed = 0 AND IsFullyInvoiced = 0 AND SalesOrderLineIsManuallyClosed = 0 AND (Salesorderlinequantity - Salesorderlineinvoiced) > 0
              the only change was upgrading from QBKS 2020 enterprise to 2021 and uprade the QODBC

              Now I removed
              Code:
              AND (Salesorderlinequantity - Salesorderlineinvoiced) > 0
              and it works perfect.
              if (Salesorderlinequantity - Salesorderlineinvoiced) > 0

              then

              Salesorderlinequantity > Salesorderlineinvoiced

              try that instead of having the computation (subtraction) performed in the query.

              I think something changed behind the scenes in one of the layers of code that happen when the query is executed.
              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

              http://www.iadn.com/images/media/iadn_member.png

              Comment


                #8
                Thanks, I agree with you on that, but it works like it is suppose to now.
                after I thought about, this is just a filter of what records to show not how many qty is left on backorder.
                I can see how your recomendation would work. I use that is field rules.
                I just was panicing because I couldn't get it to work after upgrading.
                Thanks for the help!
                I searched the forum to see if I had posted this a long time ago why I put that last line in, but couldn't find any.
                David
                A5V12.3
                Win7, 64 bit
                Qbks 2018 Enterprise
                QODBC R/W

                Comment


                  #9
                  after using this a while I would like to get rid of negitive amounts in my result
                  I have put this in
                  Code:
                  IsManuallyClosed = 0 AND IsFullyInvoiced = 0 AND SalesOrderLineIsManuallyClosed = 0
                  if (Salesorderlinequantity - Salesorderlineinvoiced) > 0
                  then
                  Salesorderlinequantity > Salesorderlineinvoiced
                  it says"Where" Clause has errors.
                  any suggestions?
                  David
                  A5V12.3
                  Win7, 64 bit
                  Qbks 2018 Enterprise
                  QODBC R/W

                  Comment


                    #10
                    Originally posted by David View Post
                    after using this a while I would like to get rid of negitive amounts in my result
                    I have put this in
                    Code:
                    IsManuallyClosed = 0 AND IsFullyInvoiced = 0 AND SalesOrderLineIsManuallyClosed = 0
                    if (Salesorderlinequantity - Salesorderlineinvoiced) > 0
                    then
                    Salesorderlinequantity > Salesorderlineinvoiced
                    it says"Where" Clause has errors.
                    any suggestions?
                    What amount is negative and why?
                    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

                    http://www.iadn.com/images/media/iadn_member.png

                    Comment


                      #11
                      the result of this formula:

                      salesorderlinequantity - salesorderlineinvoiced >0

                      I want to filter out records that have a 0 or negitive amount.

                      a customer orders 500 quantity on the sales order, we invoice for 505 quantity, so that would be a negitive number.
                      this sales order may have 10 items on the sales order and we only invoice for 1/2 of the items, so we still have backoders, I want to filter out the fully invoiced items or 0 or negitive quantity.
                      the report I print does not show the negitive items, I have filtered them out.
                      negitive.png
                      David
                      A5V12.3
                      Win7, 64 bit
                      Qbks 2018 Enterprise
                      QODBC R/W

                      Comment


                        #12
                        I suggested:
                        Salesorderlinequantity > Salesorderlineinvoiced

                        In your example the first line noted as wrong shows:
                        3500 > 4015 would be false and not included in the data.

                        Do you have Salesorderlinequantity > Salesorderlineinvoiced in your where clause?

                        Are both field's definition numeric?
                        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

                        http://www.iadn.com/images/media/iadn_member.png

                        Comment


                          #13
                          Originally posted by Al Buchholz View Post

                          if (Salesorderlinequantity - Salesorderlineinvoiced) > 0

                          then

                          Salesorderlinequantity > Salesorderlineinvoiced

                          try that instead of having the computation (subtraction) performed in the query.

                          I think something changed behind the scenes in one of the layers of code that happen when the query is executed.
                          I just copied and pasted as shown below the green line. Yes both are numeric.
                          I reached out to flexquarters and have not heard anything from them yet.
                          Where clause error2.jpg
                          David
                          A5V12.3
                          Win7, 64 bit
                          Qbks 2018 Enterprise
                          QODBC R/W

                          Comment


                            #14
                            Does this Where clause work?


                            IsManuallyClosed = 0 AND IsFullyInvoiced = 0 AND SalesOrderLineIsManuallyClosed = 0 AND Salesorderlinequantity > Salesorderlineinvoiced
                            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

                            http://www.iadn.com/images/media/iadn_member.png

                            Comment


                              #15
                              works perfect!
                              no negivetive amounts.
                              Thank you!
                              David
                              A5V12.3
                              Win7, 64 bit
                              Qbks 2018 Enterprise
                              QODBC R/W

                              Comment

                              Working...
                              X