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



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

Report.Load() ERROR: Object does not support requested interface.

  • Filter
  • Time
  • Show
Clear All
new posts

    Report.Load() ERROR: Object does not support requested interface.

    Why do these methods exist if we can't use them? I was hoping this worked similar to form.load() so I could change the report filter. I see that the properties are available in the XB explorer, just can't figure out how to access them. With my report open in design mode I can test and get a return value for the reportname.filter property in the IW, so I thought perhaps I could load the report and clear the existing filter & save it before offering the filter builder to a user who will then preview the report. I know that using a query before printing will ADD to an existing filter, I was just hoping there might be some way to also remove it programatically.

    If someone knows how - please share!

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Re: Report.Load() ERROR: Object does not support requested interface.

    Maybe you want to remove the hard coded filter from the report definition. Then conditionally add back the previously hard coded filter at print time.
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz


      Re: Report.Load() ERROR: Object does not support requested interface.

      Hi Ron,
      That is probably what I will end up doing. I was attempting to use arguments in the filter until I found I could not use those same arguments in the calculations for the report. I am using ASK variables now to get a date range which is fine unless the user wants a different filter. So I was looking for a way to perhaps set global vars when I came across the use of arguments which can be set with xbasic or if left blank, prompt the user. I just didn't want to have more versions of the same basic report.

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


        Re: Report.Load() ERROR: Object does not support requested interface.

        I'm not understanding. Why would you need more than one version of the report to handle different filters?
        There can be only one.


          Re: Report.Load() ERROR: Object does not support requested interface.

          I have a 'quick' report version where a button on a form selects the current record or provides the filter, and another version where the user creates his own query when the report is selected from a menu. Which is why using arguments seemed such a good idea since if left blank, then the user is prompted.

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


            Re: Report.Load() ERROR: Object does not support requested interface.

            Using the OnPrintInit and OnPrintExit events I came up with this for optionally prompting the user for a date range instead of using ASK vars or arguments, so these vars can be used in the report calcs:

            Calling script should dim & set the global vars b_date and e_date else if {} will prompt the user.

            dim vdate as d
            WITH global_variables()
            if b_date <> {} then
            	'skip the prompts, calling script has set the range
            	goto ENDIT
            end if
            'set the default report range to YTD
            vdate = convert_type(1+chr(47)+1+chr(47)+year(date()),"date")
            b_date = ctod(ui_get_date_calendar("Begin Date",dtoc(vdate)))
            e_date = date()
            e_date = ctod(ui_get_date_calendar("End Date",dtoc(e_date)))
            END WITH
            'report filter: 
            ' "RAP" $ SERVICE .and. between(DATE,var->b_date,var->e_date)
            'OnPrintExit clear the global date variables
            Saved this to the Code Library so my other reports using a date range can use it too.
            Last edited by MoGrace; 05-30-2018, 11:26 AM. Reason: shared doesn't work - global vars does

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford