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

Quickbooks qodbc performance

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

    #16
    Re: Quickbooks qodbc performance

    Originally posted by Jeff Fried View Post
    Al,

    That's a very good explanation regarding the way QODBC works with Quickbooks and why active link is not appropriate.

    Meanwhile, I've been doing the setup using passive link. So far it's well-behaved but I haven't gotten to the heart of it yet. One thing I noticed: I have two operations set up, one to export from the active link connection, the other to export from the passive link connection. The mere act of editing the operation has major time differences. Again, with active link, it takes maybe 15 minutes just to get into the editing window. With passive link, it popped right up. I guess it's all that real-time stuff going on with active link that keeps it real slow with Quickbooks as it works through the layers of interference while accessing the data.

    Jeff
    Jeff

    Sounds like you're on the right track. You'll be much happier with using the right tool for the job.

    The active links work well with updating QB list tables and reference tables. You will need to 'tweak' the insert/update/delete SQL from the default generic to something that fits QB.

    The QB transaction tables should be written to using Alpha DAO code instead of active links - as described in the previous message - since the Intuit SDK model requires processing that does not fit in the active link model.
    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


      #17
      Re: Quickbooks qodbc performance

      Originally posted by Jeff Fried View Post
      Very interesting. The export operation I set up to export Quickbooks data to a comma-delimited ascii file was instantaneous with the passive link setup. With active link, I may have waited 1/2 hour for it to complete.
      Because at that point it is a native dbf export.

      Originally posted by Jeff Fried View Post
      This does not include refreshing the data, which is the next test, but it is encouraging to see performance within the range of acceptability.

      The other interesting thing I noticed is that it runs silently with the passive link set up but did not with the active link set up. I don't know why this should matter, but in the end it serves the need and that's what counts.
      You can toggle the passive link refresh to run silently or noisily. You can also get information from the QODBC driver about what it is doing by turning on the driver status panel. Version 8 Alpha has a conflict with the wait dialog (passive link info from A5) and the QODBC driver status panel. Alpha 5v9 has that issue resolved.
      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


        #18
        Re: Quickbooks qodbc performance

        Al,

        I just wanted to report back first to thank you for your valuable help with active/passive link tables when working with Quickbooks and second to let you know that I have set up the procedure I was talking about for my client, using passive link tables, and the performance is quite acceptable.

        Bear in mind that there is still a processing delay while refreshing the passive link table, and this processing will be unattended (a user will not be waiting for something to happen), but it is certainly not a speed issue with the order or magnitude I experienced with active link tables used with QODBC. You have explained why active link is not appropriate for use with Quickbooks (SDK issue), so anyone anticipating use with Quickbooks is well-served to know not to go with active link tables (when it is read only).

        I guess if and when I get to the point of writing back to a Quickbooks file, I will revisit the use of active link tables for this purpose. But as you said, if used with list-type Quickbooks tables rather than transaction tables, the performance should not be an issue.

        Thanks again.

        Jeff

        Comment


          #19
          Re: Quickbooks qodbc performance

          Jeff

          Thanks for the feedback.

          And remember that refreshes should be tuned to get only the rows needed and columns - by changing the

          select * from <table>

          to

          select (list each column) from <table>

          and by adding a

          where <condition>

          These are in the passive link definition and are not to be confused with the filtering that Alpha can do once the data is loaded into the passive linked table.

          Keep us up to date on your progress and come back to the webinar to share your experiences too...
          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

          Working...
          X