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



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

xDialog - Insert option

  • Filter
  • Time
  • Show
Clear All
new posts

  • xDialog - Insert option


    How do you insert 2nd or more xDialog statements?
    vResult= UI_dlg_box("title 1",<<%dlg%
     ... do something
    If a_dlg_button = "my_event_name" then
      'I want to add 2nd xDialog form here ....
         2nd_xdialog = ui_dlg_box("more xDialog",<<%dlg%
   something for 2nd xdialg here ...
             if a_dlg_button = "my_wnd_events" then
             end if
              If 2nd_xDialog = "ok" button command here 
              ... Something ..
              end if.
    end if

  • #2
    Re: xDialog - Insert option

    You have to call a function that runs the xdialog. That function can be at the bottom of the current script/function. Of course, if it's a generic xdialog then you should put it in a separate function in the Code tab but that's probably not likely in this case.

    For example:

    script start
    vResult= UI_dlg_box("title 1",<<%dlg%
    ... do something
    IF a_dlg_button = "my_event_name"
    END IF
    ... script continues...
    script ends

    FUNCTION Second_xdialog as C ()
    <create 2nd xdialog here..


    Here's another hint -- take the %dlg% section out and make it separate like:
    dlg_text = %dlg%

    dlg_result = ui_dlg_box( "title 1", dlg_text, <<%code%

    the advantage is that the "dlg_text" is just a crlf string and you can make all kinds of modifications to it before actually displaying the xdialog. For example, you might want to display some type of count that varies from run to run. You could to that by displaying a variable in a field object but it's much nicer and more professional looking if it becomes part of the text string.

    Let's say you exported records for some reason and want to tell the user when the export is done and how many were exported ...

    ex_recs = 6

    dlg_text = <<%dlg%
    You exported [[ex_recs]] records.;

    dlg_text = stritran( dlg_text, "[[ex_recs]]", ltrim(str( ex_recs )) )

    DIM dlg_result as C
    dlg_result = ui_dlg_box( "", dlg_text, <<%code%

    The above dialog would correctly display the number of exported records whether it was 0 or 9,999,999,999. (Yeah, I know, good luck exporting that many.)

    The use of [[...]] for the variable to be replaced in the initial dlg_text string is somewhat arbitrary but not completely. It could be replaced with a simple "x" (or any other string) but we really want something that is highly unlikely to occur anywhere else and something that will show up easily if we forget to replace it. The double brackets aren't going to show up anywhere else in an xdialog and if you forget to replace them it will be very obvious in the resulting xdialog. It's also pretty obvious in the xdialog script - just look at the code above and tell me that the "[[ex_recs]]" doesn't stand out.

    The use of the same variable name inside the double brackets is also not necessary but the consistency sure makes it easier to work with.

    BEWARE, this is one of those things that will get more and more use once you get started with it.


    • #3
      Re: xDialog - Insert option

      Good Morning Cal,

      Thank you, I will try the first one.


      • #4
        Re: xDialog - Insert option

        Look into {embedded}