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 report from xdialog

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

    Preview report from xdialog

    I have a print button in my modal dialog box that previews a report layout. My problem is that the preview pops up behind the dialog box and I can't shift focus to the preview in order to print the report.

    I've experimented with using a modeless dialog box, and have the same problem.

    The only way I've found to do this is to make the dialog box modeless and then use the print button to minimize the dialog box. However, after I dismiss the preview or print the report I cannot "restore" the dialog box to it's original location and size. My only option is to maximize it, which then fills the entire Alpha Five window.

    So, how do folks do this?

    I'd like to be able to preview/print a saved report layout from a dialog box, and when the report is finished I'd like the dialog box to automatically regain focus in its original location and size.

    Is this possible?

    Thanks.

    -- tom
    Tags: None
    #2
    Re: Preview report from xdialog

    Geesh Tom, if you can't figure it out, what makes you think we can? LOL

    Why not close your dialog box when they select the print button and then use the OnPrintExit event of the report to re-open the dialog?
    Cheryl
    #1 Designs By Pagecrazy
    http://pagecrazy.com/

    Comment

      #3
      Re: Preview report from xdialog

      Good morning, Cheryl.

      Your idea is promising. I'll give it a try and let you know.

      To teach myself more xdialog this summer I decided to try to build a dialog box to manage a Phone_log table. Simple table, just to track incoming phone messages, and mark off those that have been handled. The dialog needed to be able to navigate through the table, and do the usual maintenance chores (enter, delete, edit). It needs to be able to run on a LAN with multiple users throwing records at it. I have the basic dialog almost finished. Now I'm adding "extras" like, print the current log entry. Later I hope to add other features that will permit me to change the sort sequence, do find by keys, print other reports, etc. Who knows, if the editors are interested it might turn up in the newsletter one day.

      Anyway, thanks for the suggestion. It may work, but I'd have to figure out some way to navigate to the record that just printed when the dialog opens the second time.... Otherwise, the user will have to navigate to it manually.

      -- tom

      Comment

        #4
        Re: Preview report from xdialog

        Tom,

        Capture the value of your records unique field in the OnPush of the print button and then use that variable to query the table when re-opening the dialog from the report event.

        Sounds like a cool program. You will have to let me know how it ends up.
        Cheryl
        #1 Designs By Pagecrazy
        http://pagecrazy.com/

        Comment

          #5
          Re: Preview report from xdialog

          As a variation on Cheryl's idea.

          Quote modified. Mods in bold.
          Why not Hide your dialog box when they select the print button and then use the OnPrintExit event of the report to show the dialog?PM
          UI_DLG_HIDE()

          Edit:
          Not sure if you're using the PREVIEW_REPORT() function but just noticed it has a couple of 'Modal' paramaters that may be of some help.
          Last edited by Tim Kiebert; 08-08-2006, 08:59 AM.
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment

            #6
            Re: Preview report from xdialog

            Tim's idea looks a lot easier than mine :)
            Cheryl
            #1 Designs By Pagecrazy
            http://pagecrazy.com/

            Comment

              #7
              Re: Preview report from xdialog

              Now, if only it works. :)
              Tim Kiebert
              Eagle Creek Citrus
              A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

              Comment

                #8
                Re: Preview report from xdialog

                Thanks Tim & Cheryl. The optional modal and session_modal parameters did the trick. Here's the code for the Print button:

                Code:
                    Case a_dlg_button = "Print"
    	'can only happen if rec is not dirty
	preview_report("One_msg","Callnum = "+quote(rec.callnum),"",[COLOR="Red"][U][B].t.,.t.[/B][/U][/COLOR])
    	a_dlg_button = ""
                The report is named "One_msg".
                Callnum is an autoinc identifier field (C, 5) in the table.
                Rec.callnum is a dot variable which contains the current phone call number.

                thanks again.

                -- tom

                Comment

                  #9
                  Re: Preview report from xdialog

                  Very nicely done and cleaner than mine or Tim's idea. You get 10 gold stars for that one!
                  Cheryl
                  #1 Designs By Pagecrazy
                  http://pagecrazy.com/

                  Comment

                    #10
                    Re: Preview report from xdialog

                    Cool. Glad you got it to work. I am slowly building a 'how to' file from things gleaned from the forum. This will be another entry.
                    Tim Kiebert
                    Eagle Creek Citrus
                    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                    Comment

                      #11
                      Re: Preview report from xdialog

                      I am slowly building a 'how to' file from things gleaned from the forum.
                      Can I get a copy, please, please, please :)
                      Cheryl
                      #1 Designs By Pagecrazy
                      http://pagecrazy.com/

                      Comment

                      Previous template Next
                      Working...
                      X