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

Refreshing Data

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

    Refreshing Data

    I am using the trial version of QBuilder and am having difficulty in refreshing my data. I have dowloaded the latest version and update and am still having trouble when I try and refresh. The main action I see from my computer is that it starts telling me that QReport Builder or Quickbooks is not responding and then it just seemingly does nothing until I get out of the programs. I have been successful on a few tables, but it still appears that it is not working in the most effective manner. We are using the Premier Edition (and will be going to Enterprise soon) of Quickbooks that is on a desktop server.

    Any suggestions on what I could do to make this work better would be greatly appreciated.

    Joe Quinn
    Imagic

    #2
    Re: Refreshing Data

    Joe

    Thanks for writing for help with your refresh.

    I typically use the following setup.

    1. I can use the sample data in QRB prior to refreshing the data. But it's not your data.
    So to get your own data,
    2. Have QRB and QB data on the same machine.
    3. Have QB running prior to starting the refresh. I use the DSN for the Currently Open QB file or set one up for that purpose. This will save starting QB for each table refresh.
    4. Pay no attention to the not responding message. It's a Windows message that is shown when a process passes off to another process and the response has run past a few seconds. To see what is happening, you can start task manager and select the process tab and sort on cpu.
    5. In your project directory, under My Documents,user,QReportBuilder folder the is a text file name Qreportbuilder.PL_Refresh_History. That will show details of what is going on while the refresh is proceeding.

    I find that a typical QB sample file takes 15-20 minutes to refresh all of the tables the first time. Subsequent refreshes will be somewhat faster.

    I have clients with larger QB company files. One is about 250 mb. An initial refresh of all tables takes about 4 hours. I run it overnight. The fastest refresh for that same table is about 25 minutes when only a few changes have occurred. Remember I'm refreshing all 135 some tables that are in QB.

    I'd like the refresh to be faster and performance increases are in the making. It's a top priority. On the other hand, I've measured most other competitors and found that the performance increases are not moving the decimal point but some can be faster. So I'm not looking to get a factor of 10 times faster, but some improvement under that. Hopefully the Intuit SDK will help with newer versions.

    Individual/selected table refreshes are much faster since only a few tables are done.

    This is optional at report production time depending on how recent you want your data to be. Most clients and reports are sufficient as of end of business yesterday and don't require an immediate refresh. Others do.

    hth
    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


      #3
      Re: Refreshing Data

      Al:

      Thanks for your help.

      Yes, I think I am going to move the QReportBuilder to the same machine rather than have it on my computer and accessing the QB data on the server machine and see if that helps the process.

      Glad to hear that they are working on making the refresh function run better.

      Joe

      Comment


        #4
        Re: Refreshing Data

        I know that this is an older thread, but I too am having the same problems. I am using the 2008 version of QB and am only running the trial version of QreportBuilder. QB It is located on a shared network drive, but I took the QB file home over the weekend and tried to run the update locally. Ignored the "Not Responding" prompt and it did not finish updating during the entire weekend. Over 48 hours of running.

        I would like to think that I am an anamoly in this respect. My QB db is 250+ MB but we have a fast network with gigabit wires and NIC's along with a very fast server with 15,000RPM drives and plenty of RAM on it. So, is there any idea of what I may be doing wrong?

        I have made the connection just fine. Can run an individual report, but even that takes awhile to grab the data. Just as a test I ran the update for one table, the invoice table, and it took 4.5 hours to update 13,000 invoices and did not finish.

        Any ideas would be greatly appreciated and be specific. We are pretty well verse in tech here.

        Comment

        Working...
        X