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

help with quickbooks integration

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

  • help with quickbooks integration

    I’ve created a passive link table in A5 v9 using a template In Qbuilduilder which utilizes felds in existing quickbooks reports. It was working very nicely until I upgraded to a more recent patch at which time I get an error that the syntax is incorrect.

    The syntax is as follows:

    sp_report PayrollItemDetail show Amount, Blank, Date, Name, NameAccountNumber, PayrollItem, SourceName, WageBase Parameters DateFrom = {d'2008-01-01'}

    The error message is as follows:
    Error parsing sql statement……… line 1.1 expecting “select”, found “sp_report”

    It works in qbuildbuilder just fine. It would be very time consuming to find which tables these fields are derived from.

    Any suggestions would be appreciated.

  • #2
    Re: help with quickbooks integration

    Originally posted by lmarini View Post
    The error message is as follows:
    Error parsing sql statement……… line 1.1 expecting “select”, found “sp_report”
    Lou

    Make sure that the choice for type of SQL statement type is stored procedure.
    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: help with quickbooks integration

      Thank you for the help. Being very new to sql statements, I am unable to filter a specfic date when I refresh the data. The "date from" filter doesn't appear to work. If I add an date argument, it doesn't appear to work either. Any suggestions.

      Comment


      • #4
        Re: help with quickbooks integration

        Originally posted by lmarini View Post
        The syntax is as follows:

        sp_report PayrollItemDetail show Amount, Blank, Date, Name, NameAccountNumber, PayrollItem, SourceName, WageBase Parameters DateFrom = {d'2008-01-01'}
        Originally posted by lmarini View Post
        Thank you for the help. Being very new to sql statements, I am unable to filter a specfic date when I refresh the data. The "date from" filter doesn't appear to work. If I add an date argument, it doesn't appear to work either. Any suggestions.
        Lou

        You need to have the date format look like your first example. So a simple date argument won' work. I've used an xbasic dialog to prompt for a date and then format another variable's value into {d'CCYY-MM-DD'} and then use that as a character argument.

        Hope That Helps.
        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


        • #5
          Re: help with quickbooks integration

          I fabricated the following stored procedure. I created an x-dialog date box as you described and a character variable based on that date. I placed it in the argument section but it does not filter. Quickdate2 is the character variable for date variable. Please help.

          Comment


          • #6
            Re: help with quickbooks integration

            Lou

            My fault. I forgot that the sp_report procedure doesn't allow a select statement to have a where clause. The where clause is where the filtering is done.

            I've gotten around that by using the DAO import to create the passive link table and built my own select statement with the argument already resolved.

            Something like this is the important part....

            Code:
            sql_statement=<<%sql%
            sp_report PayrollItemDetail show Amount, Blank, Date, Name, NameAccountNumber, PayrollItem, SourceName, WageBase Parameters DateFrom = :argDateFrom
            %sql%
            
            dim args as sql::arguments
            args.add("argDateFrom",vcDateFrom)   ' replace your variable in the 2nd position with the date in the format {d'CCYY-MM-DD'}
            
            Final_SQL_Statement=replace_arguments_in_string(sql_statement,args)
            ..... Use this code along with the xbasic code that DAO import provides.
            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