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

Closing the Print Preview after pressing the Print button

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

  • Closing the Print Preview after pressing the Print button

    I have an onpush event for a button on a form that prints a report for every record where the "Print" field = .T.

    Below is my code for the event. I verify the current record is saved first and then proceed to the ui_get_print_or_preview. When I select to preview the print preview comes up. I would like to have it close the preview dialog after clicking on the print button on the toolbar. Currently it just prints the report and leaves he preview window open.

    I did this in an older version (Alpha 5 V5) using the code bellow. It has been a long time since I created the old code in V5 and I can't find much information on the card_spawn function to remind me of how it worked.

    Code from current Alpha Five V11 application.
    Code:
    'str_record_change is assigned in the autoexec script
    'str_record_add is assigned in the autoexec script
    
    msg01_ui_code = UI_YES_NO + UI_STOP_SYMBOL + UI_FIRST_BUTTON_DEFAULT
    msg02_ui_code = UI_YES_NO + UI_STOP_SYMBOL + UI_FIRST_BUTTON_DEFAULT
    
    IF db_mode_get(db_current()) = 1 THEN ' change mode
    	msg01_exit_code = ui_msg_box("Warning", str_record_change, msg01_ui_code)
    	IF msg01_exit_code = 6 then
    		'Save record in current form.
    		topparent.commit()
    	Else
    		'Cancel changes to record in current form.
    		topparent.cancel()
    	End IF
    ElseIF db_mode_get(db_current()) = 2 THEN ' enter mode
    	msg02_exit_code = ui_msg_box("Warning", str_record_add, msg02_ui_code)
    	IF msg02_exit_code = 6 then
    		'Save record in current form.
    		topparent.commit()
    	Else
    		'Cancel changes to record in current form.
    		topparent.cancel()
    	End IF
    End IF
    
    record_count_y = tablecount("service.dbf","print")
    IF record_count_y = 0 then
    	ui_msg_box("Print Invoice","There are " + record_count_y + " records selected to print." + chr(13) + "Please select 'Y' in Print Y/N and try again.",16)
    Else
    	IF record_count_y = 1 then
    		ui_msg_box("Print Invoice","There is " + record_count_y + " record selected to print.",64)
    	Else
    		ui_msg_box("Print Invoice","There are " + record_count_y + " records selected to print.",64)
    	End IF
    
    	query.filter = ""
    	query.order = ""
    	
    	'Prompt user whether to print, or preview the layout. Set default to Preview 
    	prompt_result = ui_get_print_or_preview("Print ")
    	If prompt_result = "Print" then
    		
    	:Report.Print("[email protected]",query.filter,query.order)
    	
    	Else if prompt_result = "Preview" then 
    		:Report.Preview("[email protected]",query.filter,query.order)
    	End if
    end if

    Old code from Alpha Five V5
    Code:
    dim shared A_DB_CURRENT_PATH as c
    dim _DB_NAME as c
    
    'For portability, derive the secondary database name from
    'the form's database path
    _DB_NAME = A_DB_CURRENT_PATH + "SVCDAY.SET"
    
    card_spawn("print_preview", "SPAWNDB=~" + _DB_NAME + "~ SPAWNNEW=0 SPAWNCHILD=1 USE=~Invoice~ TYPE=~REP0~")

  • #2
    Re: Closing the Print Preview after pressing the Print button

    You should generate some action scripting code with version 11 and replace the old code from V5.

    You can open the form and filter in action scripting.

    While it can work with the v5 code, I've usually found that changing the code to v11 is the best idea.
    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: Closing the Print Preview after pressing the Print button

      Alan,

      Thanks for the reply, but that is what I am doing. I included in my original post my code from my V11 application. That was created using the Action Scripting. Below is the code that specivically creates the preview. The problem I have with it is that it doesn't close the preview window after clicking on the Print button on the tool bar. I was looking for a way that when in the Preview mode if you click on the Printer icon on the tool bar it would print the report and close the preview. As of right now I have to click on the print button and then click on the Exit Preview button to close it.

      Code:
      	query.filter = ""
      	query.order = ""
      	
      	'Prompt user whether to print, or preview the layout. Set default to Preview 
      	prompt_result = ui_get_print_or_preview("Print ")
      	If prompt_result = "Print" then
      		
      	:Report.Print("[email protected]",query.filter,query.order)
      	
      	Else if prompt_result = "Preview" then 
      		:Report.Preview("[email protected]",query.filter,query.order)
      	End if

      Comment


      • #4
        Re: Closing the Print Preview after pressing the Print button

        Hi Keith,

        In AlphaFive V11 you should supposedly be able to set this form the preferences settings.

        From the top menu select the following:

        View -> Settings -> Preferences -> Reports -> 'Printing from Preview Window' ..and set the value to 'Yes'



        Cheers
        Ninus

        Comment


        • #5
          Re: Closing the Print Preview after pressing the Print button

          I got around this by embedding the print preview supercontrol on a form. On a form button you can then add topparent.close(.f.)

          Comment


          • #6
            Re: Closing the Print Preview after pressing the Print button

            I was able to make the behavior function like it used to be by changing the setting as referenced by cadmen

            View -> Settings -> Preferences -> Reports -> 'Printing from Preview Window' ..and set the value to 'Yes'

            Now after clicking the print button on the print preview window that preview is closed.

            Comment


            • #7
              Re: Closing the Print Preview after pressing the Print button

              Excellent, thanks for reportback.
              Nice call Ninus.

              Comment

              Working...
              X