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

Budget Reports: error converting ResultSet?

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

    Budget Reports: error converting ResultSet?

    We're on QB Enterprise 7 with a newly downloaded version of QReportBuilder. I'm trying to a) make some custom budget v actual reports and then b) make them for multiple companies and combine the data, which is now an extraordinarily tedious serious of Excel exports. My immediate question however is simply about a) making custom budget v actual reports.

    I understand from a previous thread that the SB SDK doesn't allow direct, full access to the budget table(s), so to make budget-related reports we need to base them off of an existing QB Report.

    I've started from scratch, created a new project, and refreshed the tables from my currently open QB file, logged in with admin priviledges. All tables refresh (except payroll, which is probably because we don't have that module?).

    However, when i go to make a new Report, point it toward any one of the existing QB BudgetvActual reports, i get an error: 'Database API specific error converting ResultSet to String'. When running the reports i've tried various combinations of parameters/filters, and none at all, and nothing seems to work.

    Any advice would be much appreciated!

    Thanks,

    Lee

    #2
    Re: Budget Reports: error converting ResultSet?

    Originally posted by plumtv View Post
    We're on QB Enterprise 7 with a newly downloaded version of QReportBuilder. I'm trying to a) make some custom budget v actual reports and then b) make them for multiple companies and combine the data, which is now an extraordinarily tedious serious of Excel exports. My immediate question however is simply about a) making custom budget v actual reports.

    I understand from a previous thread that the SB SDK doesn't allow direct, full access to the budget table(s), so to make budget-related reports we need to base them off of an existing QB Report.

    I've started from scratch, created a new project, and refreshed the tables from my currently open QB file, logged in with admin priviledges. All tables refresh (except payroll, which is probably because we don't have that module?).
    That is correct. But the latest version of QRB shouldn't try to access Payroll if you don't have a Payroll subscription.

    Can you look at the help - About QReportBuilder and tell me the version and build numbers that are shown?

    Originally posted by plumtv View Post
    However, when i go to make a new Report, point it toward any one of the existing QB BudgetvActual reports, i get an error: 'Database API specific error converting ResultSet to String'. When running the reports i've tried various combinations of parameters/filters, and none at all, and nothing seems to work.

    Any advice would be much appreciated!

    Thanks,

    Lee
    This may be another sign that you don't have the latest version..

    See the attached image to show the version and build numbers.

    Beyond that, you will need to build a report(table) for each company file that is to be merged and have the connection string specifically open the company table. Then an append operation can combine all of the tables together or a set can combine all of the tables together.

    You may want to stop in the Thursday webinar and see some of the steps in action....
    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: Budget Reports: error converting ResultSet?

      I had trouble getting the budget from QB also (kept getting an error). I ended up making my own tables with the budget data in them and linked them to the Profit and Loss QB tables to build the reports. Don't know if this will help.

      Comment


        #4
        Re: Budget Reports: error converting ResultSet?

        Originally posted by wsrcd View Post
        I had trouble getting the budget from QB also (kept getting an error). I ended up making my own tables with the budget data in them and linked them to the Profit and Loss QB tables to build the reports. Don't know if this will help.
        Jessica

        That is a good work around. I've found that the issue is a slight ( but sufficient) problem with the fiscalyear prompt. It is making FiscalYear = '2008' when it should be FiscalYear = 2008

        So, make a passive-linked table from the linked/import external data sources under the data - more options choice.

        Attached is an example of an SQL statement that I use for a report.

        Hope that explains it for now. A fix is in the works, but no timetable is set at this point. Please use the work around for now.
        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