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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Preview prompts twice.

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Preview prompts twice.

    I have a fairly long script that prints any one of about 17 reports. To save script space, I created a Print_it function that does the Preview/Print prompt and then runs the preview or print as requested.

    The weird thing is that there are always two prompts before the preview is shown - but only one prompt when printing without a preview. HOWEVER, if I copy the exact code that is in the function and run it as part of the script, only one prompt is shown.

    An example script is shown below. It should even work on your own system if you just change the report name to a valid name in your own app - see the line rname = "xxx". I will attach the same script in a text file where it will be easier to read and/or copy to your code editor.

    FUNCTION print_it as C( rname as C )
    print_type = ui_get_list( "PRINT TYPE", 1, "Preview First", "Direct to Printer" )
    IF print_type = ""
    EXIT FUNCTION
    END IF

    SELECT
    CASE print_type = "Preview First"
    report.preview( rname )
    CASE print_type = "Direct to Printer"
    report.print( rname, filter, order )
    END SELECT
    END FUNCTION

    'Using the function, I always get 2 preview/print prompts.
    rname = "CMR51_BONUS_Pool"

    'REM out the next two lines to test it without the function.
    print_it( rname )
    END

    'If I replace the function call with the following, there is only one prompt.
    'NOTE: This is copied directly from the function except EXIT FUNCTION is now END.
    print_type = ui_get_list( "PRINT TYPE", 1, "Preview First", "Direct to Printer" )
    IF print_type = ""
    END
    END IF

    SELECT
    CASE print_type = "Preview First"
    report.preview( rname )
    CASE print_type = "Direct to Printer"
    report.print( rname, filter, order )
    END SELECT

    END
    Tags: None
    #2
    RE: Preview prompts twice.

    Some days I hate computers.

    Mine crashed just as I was trying to select the file attachment - so I assumed it didn't get sent and rewrote the whole thing in a text editor this time so I could save it as I wrote it. Then I opened up the message board to find out I had wasted my time - argh!

    Anyway, here's the attachment - along with my second version of the message.

    Comment

      #3
      RE: Preview prompts twice.

      WHERE'S MY SLEDGE HAMMER!!

      Apparently there's a problem in the file lookup window. I have to scroll over through many files and it keeps locking up my system just before it gets to the one I want. I added "A_" to the beginning of the file name so it will appear at the start of the list. Maybe it will work this time.

      Comment

        #4
        RE: Preview prompts twice.

        Cal,

        How do the values for filter and order get passed to the function, so they can be used by the direct print select case statement?

        -- tom

        Comment

          #5
          RE: Preview prompts twice.

          Sorry, I meant to take all references to filter and order out of the script when I simplified it. Forgot to do it in the Direct to Printer option.

          You can take out the references - or, my original function def. was:

          FUNCTION print_it as C( rname as C, filter="" as C, order="" as C )

          By the way, the same problem was occurring in version 4.5 but I knew we would soon be changing to v5 so I didn't bother with it at the time.

          Comment

            #6
            RE: Preview prompts twice.

            i don't really know the answer, but i have a solution.

            it certainly is strange.

            the solution is to put in an xbasic_wait_for_idle() immediately after the function command. e.g.

            FUNCTION print_it as C( rname as C )
            xbasic_wait_for_idle()

            Comment

              #7
              RE: Preview prompts twice.

              Thanks Selwyn - glad to know this wasn't just on my machine this time!

              Comment

              Previous template Next
              Working...
              X