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

How can I refresh a print preview screen when underlying data changes.

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

    How can I refresh a print preview screen when underlying data changes.

    Attached is an example of the scenario.
    When the sample DB loads it opens on a simple form to check/edit details and to preview the invoice

    At first view the invoice is not yet posted and has no inv number when previewing.
    TO accept, pressing a button on the preview will process the invoice and issue an invoice number.

    All works as explained so far. The underlying invoice table has been updated BUT..

    ...the preview remains unchanged -
    if the user then prints, it will not be an invoice conforming to TAX requirements as it does not have the invoice number and is still worded "Preview"

    Even though the underlying data has changed, the user now has to close the preview, refresh the form and go back into preview (now with all the requirements showing) , print and again close the preview.


    If the preview can be resynched,
    or closed and re-opened automatically that would provide a solution.
    Any way possible? or any other suggestions?
    Attached Files

    #2
    Re: How can I refresh a print preview screen when underlying data changes.

    I doubt that is possible. The print preview is imaged using the chosen print driver. Don't see how that can be refreshed.

    You might be able to fake a print preview using a form designed to mimic the invoice.
    Last edited by Stan Mathews; 01-19-2013, 06:55 PM.
    There can be only one.

    Comment


      #3
      Re: How can I refresh a print preview screen when underlying data changes.

      Try this put it in a new folder:
      Attached Files
      Last edited by Allen Klimeck; 01-20-2013, 04:14 PM.

      Comment


        #4
        Re: How can I refresh a print preview screen when underlying data changes.

        Apologies both - I did not get email notices. MS has shut down my outlook (expired) but I seem to still receive mail. Researching an alternative, anyway...

        Stan thanks, I had thought that as an option but it won't satisfy all conditions.
        So its seems problematic (I've tried all kind of ways) to close a preview with xbasic? What does menu item "Close preview" do I wonder.

        I am about to download and look your option Allen, thanks so far.

        Report back soonest.

        Comment


          #5
          Re: How can I refresh a print preview screen when underlying data changes.

          Stunning Allen K brilliant.
          That was certainly worth the effort putting the demo together to receive a ready working solution.
          I salute you thanks for your effort.
          Is it all done here?

          Code:
          preview__invxtst.close(.t.)
          InvXtestprint.Activate()
          InvXtestprint.resynch()
          dim shared currecn as n
          currecn = current_record_number()
          PREVIEW_REPORT("InvXtst","recno() = " + currecn,"",.f.,.f.)
          I must check if you made changes to the inv_commit code

          Comment


            #6
            Re: How can I refresh a print preview screen when underlying data changes.

            Ray I had to change the preview_report() so that the print preview would be modeless. There seems to be an error in the documentation as the first .t. causes a modal preview as I would have expected but the doc's say the opposite. I couldn't find a way to close the preview if it was modal. There has to be a way though. I also commented out some code from your script that was attempting to update the form & put it on the button.

            So I changed:

            PREVIEW_REPORT("InvXtst","recno() = " + currecn,"",.t.,.t.)
            on the button on your form to:

            PREVIEW_REPORT("InvXtst","recno() = " + currecn,"",.f.,.f.)

            added the code you found and commented out:

            'pob=obj("InvXtestprint")
            'pob.Resynch()

            in the inv_commit script.

            You might want to change:
            preview__invxtst.close(.t.)
            to:
            this.close()

            And keep in mind that using “InvXtestprint” in the script might fail if some how the user has the form open twice. As the first instance will be named “InvXtestprint” and the second will be “InvXtestprint0”. The same thing can happen to the preview.
            Last edited by Allen Klimeck; 01-20-2013, 04:13 PM.

            Comment


              #7
              Re: How can I refresh a print preview screen when underlying data changes.

              Brilliant All good.
              The full systems launch menu ensures that only one copy of the form is ever loaded per user. Good point made.

              Comment


                #8
                Re: How can I refresh a print preview screen when underlying data changes.

                Originally posted by Allen Klimeck View Post
                .. I couldn't find a way to close the preview if it was modal. There has to be a way though..
                Pity. I will keep looking
                I can however in the meantime circumvent this on the Print/Preview button with
                Code:
                if is_object("Invoiceprintform")
                	preview__invoiceprintform.close(.t.)
                end if
                borrowed from your sample.
                (In the live version 'invoiceprintform' is the print layout name)

                Comment


                  #9
                  Re: How can I refresh a print preview screen when underlying data changes.

                  Just a thought, don't know if it's possible in Version 10. Embedded report in the form will refresh the report.

                  Cornelius

                  Comment


                    #10
                    Re: How can I refresh a print preview screen when underlying data changes.

                    It is in V10
                    That presents some very interesting possibilities

                    Comment


                      #11
                      Re: How can I refresh a print preview screen when underlying data changes.

                      Ray,
                      If you are using the report super control and looking for interesting possibilities, this may be of interest to you.
                      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


                        #12
                        Re: How can I refresh a print preview screen when underlying data changes.

                        Thanks Tim.
                        I have bookmarked that page for when I get the current project finished - a bit pressed right now to explore.

                        If you have a few minutes would you describe what your drilldown could provide, as a for example?
                        I would appreciate that.

                        Comment

                        Working...
                        X