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

Refresh table fails

  • Filter
  • Time
  • Show
Clear All
new posts

  • Refresh table fails

    I am trying to refresh a couple of LARGE tables. I am getting the following Error.

    Could not create local cache for data from your Database. Your Database reported the following error:

    Database API specific error

    Your database has returned the following error code and description to Alpha Five.
    Consult your database documentation for further information.

    10004 - '[QODBC] Error
    SQL State is: 42500 while converting ResultSet to DBF table'

    This is pretty much gibberish to me and doesn't offer any clue as to why this report, which has ran at the end of every quarter this year, with out fail, now gets this cryptic error message.

    Does anyone have any ideas what I need to do to get around this error? I need to have this report ran by the end of the week.

  • #2
    Re: Refresh table fails

    Hi Pat,
    Does the error also occur now when accessing a lessor record set which was successful before? Not knowing how you are obtaining records determines how to try and check this out.---if you take all the records when refreshing try adding a date range to limit the records coming over (may want to do this anyway as a matter of course).

    Your OS speed (cpu, ram, etc) may even play a part.

    I had one client whose report would not run correctly (if at all) until he upgraded to QRB v11. Why? It could have been a couple of things, but both I am assuming are due to the processing speed of the huge amount of data coming across....Will you have to do this? We will have to explore much further to determine if so. If you do need to test out in v11 you can download the trial version of it--BUT make a copy of your project first and open that--creating a back up also would be prudent. Once opened in v11 your project may not function correctly in a prior version dependent upon what your project has in it I have found. So I would do this as a last course of diagnostic if uncomfortable doing so.

    Other pertinent information that should be given....what else have you tried?

    Compacting Database?
    QRB complete shutdown--restart?
    Rebuilding Indices?

    Some/all of the above may be above your understanding and, if so, going off-board with this may be a possibility to try and diagnose this issue. Private message me if needed as it would take but a few minutes to do some of the testing if the error shows up in a relatively short time period.

    Al Buchholz may have an idea or two as well when he sees this.
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau


    • #3
      Re: Refresh table fails

      I spoke with Pat and gave him a couple of suggestions that he will try when the workload allows.

      We'll post a follow up with the results.
      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.