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

Printed message in report based onto variable defined previously in Xdialog

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

    Printed message in report based onto variable defined previously in Xdialog

    Any help appreciated how to transfer a variable value from Xdialog into a report.
    E.g. Xdialog asks the user what kind of message text the user wants to print into the report, like e.g. choices Message1, Message2, Message3, Message4..... . If the I chose Message3, how to transfer the Message3 variable value into the report where the report cd then do a calculated field with e.g. printout=lookupc("F", Message3,"MessageText",....) to find into the messages table which text to print out ?

    #2
    I'm confused by your reference to a variable, then mentioning a lookupc() to a message table to get the message....

    1. If it's in the message table, then define a set with the report data tables and the message table linked properly. Then you have a field to display the message.
    The xdialog can prompt for the message value and write to the message table, or you can have a form/browse to the message table where you maintain the values of the messages.
    A field in the report data where you select the message you want can handle the display of the selected message. Having that field in the data table keeps a record what was chosen. Then if the message table changes in the future, you have a audit of what message was actually used for this report..

    Personally that's the way I handle messages in reports.
    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
      Al, let me try to explain differently:

      a) Let say I hv message.dbf with two character fields LANGUAGE and MESSAGE. Into it you hv then e.g. records like "EN" "This is the message", "DE" "Das ist die Nachricht", "HR" "To je poruka", "SI" "To je obvestilo", "HU" "Ez egy ertesites" .....

      b) Then you hv an Xdialog fired by a button onto the documents form of the docs.set (documents like e.g. Booking info, Notice of Sailing, Shipment info, Notice of arrival, Truck dispatch info...) where the user is asked in which language the message shd be printed onto the report, and let say user choses radio button for "DE" (despite the form itself shows and shd remain to show all data in EN(glish).

      c) Then you hv the report which shd print the message in the Xdialog chosen language. My problem is that I don't know how to program that the report "gets to know" what language was chosen in Xdialog/how the language value can be transferred directly from Xdialog into the report. Cos the LANGUAGE filed in the docs.set form is EN, but the report I want to print the DE message (cos I want to email to a German speaking colleague)

      Comment


        #4
        Originally posted by Ales View Post
        Al, let me try to explain differently:

        a) Let say I hv message.dbf with two character fields LANGUAGE and MESSAGE. Into it you hv then e.g. records like "EN" "This is the message", "DE" "Das ist die Nachricht", "HR" "To je poruka", "SI" "To je obvestilo", "HU" "Ez egy ertesites" .....

        b) Then you hv an Xdialog fired by a button onto the documents form of the docs.set (documents like e.g. Booking info, Notice of Sailing, Shipment info, Notice of arrival, Truck dispatch info...) where the user is asked in which language the message shd be printed onto the report, and let say user choses radio button for "DE" (despite the form itself shows and shd remain to show all data in EN(glish).

        c) Then you hv the report which shd print the message in the Xdialog chosen language. My problem is that I don't know how to program that the report "gets to know" what language was chosen in Xdialog/how the language value can be transferred directly from Xdialog into the report. Cos the LANGUAGE filed in the docs.set form is EN, but the report I want to print the DE message (cos I want to email to a German speaking colleague)
        My design would be a people table that would have a field with the language code for their normal language.

        Then a set that has people linked to the message table using the normal language code.

        That's the simple way forward. Other table that are need would be in the set above or below the people/language tables.

        And/or you may also need to have the language code in the other tables you mentioned so you can use different languages for each document type. Then link accordingly.
        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

        Working...
        X