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

Form printing

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

    Form printing

    Anybody out there solved the problem of manipulating the printer setup dialog box with xbasic, action scripting or another way in A5V3?? Here's the problem:

    Have several forms where some are used to print only the current record while others are used to print several hundred pages of records, one form to a page. On forms where only the current record is to be printed I have a button to print such and do not have the form properties include bringing up the printer setup dialog box as it is really just another step to do. On forms involving multiple pages (records) the form properties do have the printer dialog box come up so each print run can be matched with printer paper capacity etc. IE:May have to print 400 records but want to do 1-200 and then 201-400 as the paper capacity is only 200 sheets.

    The problem comes when I have just finished the 201-400 run and return to printing a another form calling for only the present record is to be printed. The print range in the printer setup does not reset to "all" and is still effectively set at "pages 201 to 400". Consequently, it won't print the current record when called for. Of course if the form properties are set again so the printer dialog box comes up on printing, the range can be changed and it will print the current record. The ratio of printing the current record to the multiple records printing is probably 50 or 100 to 1 so having the dialog box up every time is a pain.

    The ideal would be to reset the print range from "X toY pages" to "All" every time the current record printing forms are opened with a script. I've searched the Xbasic ref manual and action scripting info high and low but no way to do this is apparent to me. Have I missed something or is there another way???????
    Tags: None
    #2
    RE: Form printing

    Ken,
    You'll have more control over printing if you output the data using reports than you will using forms. Then you can set the records to be printed using ask_variables (quick and dirty) or create another form to accept the records to be printed as variables and use those variables in the report filter. You can duplicate the layout of your form in the report so they'll look the same.

    Comment

      #3
      RE: Form printing

      Ohlen:
      I think you will find that printing the data either as reports or forms, the same problem remains with the print range box on the printer dialog box - it stays in the last used mode and does not reset to "all". So again one would have to have it come up (for correction of the print range the first time after multiple page printing and just to hit the OK button thereafter)creating an extra step on the several printings requiring just one record. The only way I've found to actually reset it is exit A5 and restart which isn't practical. The other workaround which isn't too much better is to instruct the operator to go back and print an extra page 1 of 1 after multiple page printing. I wouldn't be surprised that you have to get into the windows print driver to do exactly what I want.

      Any other ideas???

      Thanks

      Comment

        #4
        RE: Form printing

        Hi Ken,
        Obviously, I don't understand the extent of your problem. However, I have several reports where I allow the operator to pick the starting record so if the print fails somewhere, they don't have to start all over again. I just put a filter in the report definition and filter the records by the record number (not the system recno(), but by an assigned number). Why can't a similar thing work for you?
        Ohlen

        Comment

          #5
          RE: Form printing

          Ohlen:
          Maybe I'm not making my problem clear. But The short of it is that I don't want to have to open the printer setup dialog box on forms/reports where I am only going to print a single record while still insuring that it is set to print "all" or "page 1 of 1". Since it appears to default to the last print setup, this will not always be the case if some form of multiple page printing was last done. If it is not set to either of these settings it will not print a single record. The single record printings are invoices done at time of sale. Opening the print setup dialog box for each invoice is inefficient.

          When the operator is printing several hundred forms/reports a few hundred at a time, the records are already filtered out of thousands so the numbering scheme isn't easily implemented in my mind without creating a new table, etc. The multiple printings represent followup notices based on dates and logical fields.

          All of this printing is being done by relatively unskilled operators so keeping a few steps as possible is desirable.

          I really want to get at that print setup behind the scenes and reset it but don't see how.
          kcb

          Comment

            #6
            RE: Form printing

            OHHHHH Boy!

            I'm still not understanding the whole of this; so, if you want to give up trying to explain it, I don't blame you.

            In my app I have several reports which are always 1 page. I click on the button and the single page prints. Other reports are multiple pages; I click on the button and the report prints all the pages. I never let the operator see the printer setup dialog; it's set to always print all the pages. The printer prints however many pages are in the report. I don't see why it's necessary to get to the printer dialog to specify the number of pages.

            Comment

              #7
              RE: Form printing

              Ah yes - in your case the printer setup can remain at "all" and everything will be fine. But in this case most of the time only one page is printed too but then again up to 2500 pages may be run. In the 2500 (filtered from several thousand) case they want to break up the printing in 200 page increments and to do so must use the setup dialog box. If it is last used to print pages 2300-2500 and they go back to a one page report, it will not print unless the setup is changed to "all" or "page 1 of 1" which I don't want to have to do at each single page printing as it remains in last mode used. Therefore, I would like to be able to reset it with a script or other means unknown to me.

              The bottom line is I don't want to open the setup dialog on the one page reports but somehow must insure it is in a mode which will print. Does this help??
              ken

              Comment

                #8
                RE: Form printing

                Ah-ha! The light comes on.

                So, why can't you do it with variables? If records are numbered, have the operator select, say record var->start to var->end and then set the report definition to allow only records between the 2 variables? Or, if alphabetical, last names from K through N, or something like that?

                Comment

                Previous template Next
                Working...
                X