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

Printing a form/w variables;

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

    Printing a form/w variables;

    I have a form/w about 20 different variables on it. The form has a 'start' button which calls a script (script_play_local). After the script looks through many rcrds in many DB'S, it finally comes up with the variables values. It assigns the values to the variables assigned to the form and then refreshes the form.

    All variables are shared and show up just fine on the form in the background, but when the script calls for print.preview(), or form.print(), the form does not print out or preview with any values in the variables? Another words, just a blank/w text fields.

    I've tried to get a pointer to the form but that didn't work. I tried parent with no avail. I am probably doing something stupid and have been staring at it long enough to totally miss something simple.

    Can anyone possibly help?

    Mac
    Tags: None
    #2
    RE: Printing a form/w variables;

    Hello Mac,

    ""All variables are shared ""
    Local and shared variables are not available beyond a session's bounderies, unless you explicitly pass them or a pointer to them. A simple approach would be to make them global in scope, but that is not the best approach. In the Alpha Help chm file, on the index tab, type in:

    local_variables

    and you will get a very informative page that will show you how to pass the various variable namespace's around.

    Good luck,
    Jim

    Comment

      #3
      RE: Printing a form/w variables;

      Mac,

      The report engine is much more robust than the form print routines. I recommend you use a report layout and then print the report, instead of the form. -- tom

      Comment

        #4
        RE: Printing a form/w variables;

        Jim,

        Let me try again please; The script has done it's job and the variables do have their respective values on the form. What is happening is, when I try to print or preview, the form loses all the values or the variables are gone? I'm not sure? The printer will print a blank form with just the text lines within it. I double checked to make sure that the 'hide' or 'disable' box was not checked on their properties.

        I guess you probably can tell I'm not the best programmer here, but I've been working on this application since 1996 with AlphaFive V1.0.2. Now I'm trying to convert to A5V5.

        POINT: Jim, I must tell you that there are no fields relative to the main DB here. The form is embedded with only variables and txt lines. That's why it would be improbable to use a report. I pull the data from values stored within the DB's.

        Did I help any Jim?

        Mac

        Comment

          #5
          RE: Printing a form/w variables;

          Hello Mac,

          ""POINT: Jim, I must tell you that there are no fields relative to the main DB here. The form is embedded with only variables and txt lines. That's why it would be improbable to use a report. I pull the data from values stored within the DB's. ""

          This doesn't make any difference. I would approach it using a report, as Tom suggested. IMHO that would be easier and give you much more 'printout power'. But that also is a different matter. When you bring up a print routine, whether it is print preview or print, you are starting a new session. As I mentioned in the post, local or session variables in one session are not visable in another session. That is why you have to explicity point to or pass the variables. Again, if you declare the variables as global, it should work fine.

          Good luck,
          Jim

          Comment

            #6
            RE: Printing a form/w variables;

            Jim,

            I must not be paying attention - I don't think I found anywhere in the help files that actually stated that a print.preview or print.report started a new session. This must be old hat stuff that I never paid attention too.

            I will approach this with a different look now. I'll get back at you if I figure it out.

            Thanks a bunch

            Mac

            Comment

              #7
              RE: Printing a form/w variables;

              Jim,

              I found out that changing the variables in the form and in the script to 'global' and changing the ':form.print() to the old command :form.print(A_FORM_CURRENT)did the trick.

              Thanks for your help Jim,

              Mac

              Comment

              Previous template Next
              Working...
              X