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

Print on custom toolbar

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

    Print on custom toolbar

    I am using a custom toolbar on a po program that I am doing for a school in our district. When I press print on the toolbar, the option of printing or preview comes up the I get an error:
    Script: TEMPLATE line8:
    review_report("po",query.filter,query.order)
    Function is not recognized

    Here is the xbasic that I placed in the custom toolbar for printing:

    record_number = current_record_number()
    query.filter = "recno() = " + record_number
    query.order = ""
    prompt_result = ui_get_print_or_preview("preview ")
    if prompt_result = "print" then
    rint_report("po",query.filter,query.order)
    else if prompt_result = "Preview" then
    review_report("po",query.filter,query.order)
    end if

    Please give some direction.

    Thanks as always,

    ted
    tsoileau is online now Report Post Edit/Delete Message

    #2
    Re: Print on custom toolbar

    Have p's been dropped?

    rint_report() s/b print_report()

    review_report() s/b preview_report()

    Comment


      #3
      Re: Print on custom toolbar

      Tom,

      The p's didn't carryover from copy and paste. They are in the toolbar script.

      Comment


        #4
        Re: Print on custom toolbar

        After correcting the spellings I adapted your script to a custom toolbar for the Customer information form in AlphaSports and it ran just fine. Suggest you double check the spelling of the preview and print function calls. Might be prudent to check the spelling of the report name, too.

        Comment


          #5
          Re: Print on custom toolbar

          Tom,
          This is what it should have looked like on the original post. The p on print was left off with the copy and paste. "PO" is the name of the report that I would like to print.
          What I did do is replace this script with: a5_print_current_record() It does work except that I would like to just allow the report to print and eliminate the other choices. I do not understand how the script works ok for you but not for me. I guess I am not seeing the forest through the trees.

          Thanks for your response.



          record_number = current_record_number()
          query.filter = "recno() = " + record_number
          query.order = ""
          prompt_result = ui_get_print_or_preview("preview ")
          if prompt_result = "print" then
          print_report("po",query.filter,query.order)
          else if prompt_result = "Preview" then
          review_report("po",query.filter,query.order)
          end if

          Comment


            #6
            Re: Print on custom toolbar

            Ted,

            Can you send the whole step by step? It seems there is more to it.

            Code:
            record_number = current_record_number()
            query.filter = "recno() = " + record_number
            query.order = ""
            prompt_result = ui_get_print_or_preview("preview ")  '[COLOR=red]where did this prompt come from  "[COLOR=red]prompt_result"[/COLOR]?[/COLOR]
            if prompt_result = "print" then
            rint_report("po",query.filter,query.order)
            else prompt_result = "Preview"   [COLOR=red]'then  not needed ?
            [/COLOR]review_report("po",query.filter,query.order)
            end if
            
            [COLOR="DarkRed"]My code to print a christmas card if it helps.  Most was stolen off a button made by alpha.[/COLOR]
            dim flag_error as l
            flag_error = .f.
            if is_object(topparent.this) then 
            	p = topparent.this
            	if p.class() = "Form" then 
            		DELETE Parameter1 
            		'Set the Parameter variable to the object's .value property
            		Parameter1 = eval("P:Acct.value")
            	else    'Not in a Form. This is an error condition.
            		flag_error = .t.
            	end if 
            else
            	flag_error = .t.
            end if 
            if flag_error then 
            	ui_msg_box("Error","You can only run this script from within a Form",UI_STOP_SYMBOL)
            	end 
            end if 
            filter = "Acct = [varN->parameter1]"
            query.filter = replace_parameters(filter,local_variables())
            query.order = ""
            :Report.Print("CCardsPrint1",query.filter,query.order)
            Or maybe I am wrong, maybe will know when we see it all??

            I really cheat on this stuff by letting alpha do the joband then copying the code after I have it working in a button tht alpha does for me.
            Last edited by DaveM; 12-15-2009, 06:58 PM.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment


              #7
              Re: Print on custom toolbar

              I tried something new today and low and behold it worked.
              Tom and Dave, thanks for your help. Dave, like you, I try to use Alpha to write the code and then view it. Unfortunately, sometimes it is like trying to find your glasses when they are sitting on your nose.

              I hope you guys have a Merry Christmas and a Happy New Year.

              Ted

              Comment


                #8
                Re: Print on custom toolbar

                I tried something new today and low and behold it worked.
                What did you try? Future viewers of the thread may be interested in your solution.

                Comment


                  #9
                  Re: Print on custom toolbar

                  I used the following code by letting alpha do it then coping it to the tool bar.

                  record_number = current_record_number()
                  query.filter = "recno() = " + record_number
                  query.order = ""



                  'Prompt user whether to print, or preview the layout. Set default to Print
                  prompt_result = ui_get_print_or_preview("Print")
                  If prompt_result = "Print" then

                  :Report.Print("PO",query.filter,query.order)

                  Else if prompt_result = "Preview" then
                  :Report.Preview("PO",query.filter,query.order)
                  End if

                  Works like a charm. This will print the current record in the report.

                  Again, thanks to all for the help.

                  ted

                  Comment

                  Working...
                  X