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

Combing two Xdialog Boxes

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

  • Combing two Xdialog Boxes

    I am working on a dialog that asks for a field name in a defined table and then a value from that field:

    DIM SHARED vFieldName as c
    DIM SHARED varC_result as C
    DIM SHARED vFieldValue as C
    DIM vFieldValue_rl_def as C

    varC_result = ui_dlg_box("Field Selection",<<%dlg%
    {region}
    Name:| [%p=ui_get_fieldname("base_details","VFieldName");I=$a5_smart_field%.40vFieldName];
    {endregion};
    {line=1,0};
    {region}
    <15OK!OK> <15Cancel!CANCEL>
    {endregion};
    %dlg%)
    VFieldValue_rl_def = "k=base_details,{keylist_build("H=.05,1:25,2:25",''+"+vFieldName+",left(''+"+vFieldName+",25),left(''+"+vFieldName+",25))}{}"
    varC_result = ui_dlg_box("@="+vFieldName,<<%dlg%
    {region}
    Entry:| [%@VFieldValue_rl_def%.40VFieldValue];
    {endregion};
    {line=1,0};
    {region}
    <15OK!OK> <15Cancel!CANCEL>
    {endregion};
    %dlg%)
    I can get it to work using the two example xdialogs as above. Is it possible to combine both in one Dialog? If so, how is it done?
    been away from coding for a while so am very rusty :)
    --
    Support your local Search and Rescue Unit, Get Lost!

    www.westrowops.co.uk

  • #2
    Re: Combing two Xdialog Boxes

    Graham,

    Is the second dlg working xdlg?
    VFieldValue_rl_def = "k=base_details,{keylist_build("H=.05,1:25,2:25",''+"+vFieldName+",left(''+"+vFieldName+",25),left(''+"+vFieldName+",25))}{}"
    varC_result = ui_dlg_box("@="+vFieldName,<<%dlg%
    {region}
    Entry:| [%@VFieldValue_rl_def%.40VFieldValue];
    {endregion};
    {line=1,0};
    {region}
    <15OK!OK> <15Cancel!CANCEL>
    {endregion};
    %dlg%)

    Comment


    • #3
      Re: Combing two Xdialog Boxes

      Graham,

      I did this way.
      Code:
      'Create an XDialog dialog box to prompt for parameters.
      DIM SHARED vOption as C
      DIM SHARED vddwn as C
      DIM SHARED vddwn2 as C
      DIM SHARED varC_result as C
      ok_button_label = "&OK"
      cancel_button_label = "&Cancel"
      
      DIM vddwn_rl_def as C 
      '// created with action_script and arranged it
      'vddwn_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25[Base]\",''+base,left(''+base,25))}{}"
      'DIM vddwn2_rl_def as C 
      'vddwn2_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25[Unique]\",''+unique,left(''+unique,25))}{}"
      
      
      vOption ="base"
      if vOption ="base" then
      	vddwn_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25[Base]\",''+base,left(''+base,25))}{}"
      else
      	vddwn_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25[Unique]\",''+unique,left(''+unique,25))}{}"
      end if
      
      varC_result = ui_dlg_box("select value",<<%dlg%
      {region}
      {region}List option:{endregion}|
      {region}
      (vOption:base!vOpt_changed);
      (vOption:unique!vOpt_changed);
      {endregion};
      ;
      {endregion};
      
      {region}
      select one:| [%@vddwn_rl_def%.40vddwn];
      
      {endregion};
      {line=1,0};
      {region}
      <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
      {endregion};
      %dlg%,<<%code%
      if a_dlg_button ="vOpt_changed" then
      	if vOption ="base" then
      		vddwn_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25[Base]\",''+base,left(''+base,25))}{}"
      	else
      		vddwn_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25[Unique]\",''+unique,left(''+unique,25))}{}"
      	end if
      	vddwn_rl_def = replace_parameters(vddwn_rl_def,local_variables())
      	a_dlg_button =""
      end if
      %code%)
      you have missed "\" in your second dlg code.
      see this example.
      Code:
      vddwn_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25[Unique]\",''+unique,left(''+unique,25))}{}"

      Comment


      • #4
        Re: Combing two Xdialog Boxes

        Originally posted by johnkoh View Post
        Graham,

        Is the second dlg working xdlg?
        Yes
        --
        Support your local Search and Rescue Unit, Get Lost!

        www.westrowops.co.uk

        Comment


        • #5
          Re: Combing two Xdialog Boxes

          I can see that that works, but it gets complicated when there are 16 fields to choose from!
          --
          Support your local Search and Rescue Unit, Get Lost!

          www.westrowops.co.uk

          Comment


          • #6
            Re: Combing two Xdialog Boxes

            Thanks John,
            your code pointed me in the correction direction:

            DIM SHARED vFieldList as C
            DIM shared vFieldValue as C
            DIM SHARED varC_result as C
            vFieldValue_def = "k=base_details,{keylist_build("H=.05,1:25[]",''+"-vFieldList-",left(''+"-vFieldList-",25))}{unique_key_value()}"
            varC_result = ui_dlg_box("Select From Following Fields",<<%dlg%
            {Background=#0+204+255}
            {region}
            {region}List:{endregion}|
            {region}(VFieldList:Ati_Code!vFieldList_changed);
            (VFieldList:Base!vFieldList_changed);
            (VFieldList:C1!vFieldList_changed);
            (VFieldList:Country!vFieldList_changed);
            (VFieldList:County_Name!vFieldList_changed);
            (VFieldList:District_Name!vFieldList_changed);
            (VFieldList:Faa_Code!vFieldList_changed);
            (VFieldList:Iata_Code!vFieldList_changed);
            (VFieldList:Icao_Code!vFieldList_changed);
            (VFieldList:Old_Code!vFieldList_changed);
            (VFieldList:Other_Code!vFieldList_changed);
            (VFieldList:Other_Name!vFieldList_changed);
            (VFieldList:Place_Name!vFieldList_changed);
            (VFieldList:Province_Name!vFieldList_changed);
            (VFieldList:Region_Name!vFieldList_changed);
            (VFieldList:User1!vFieldList_changed);{endregion};
            ;
            {endregion};
            {line=1,0};
            Value:| [%@vFieldValue_def%.40vFieldValue];
            {region};
            <*15OK!OK> <15Cancel!CANCEL>
            {endregion};
            %dlg%,<<%code%
            if a_dlg_button ="vFieldList_changed" then
            vFieldValue_def = "k=base_details,{keylist_build("H=.05,1:40["-VfieldList-"]",''+"-vFieldlist-",left(''+"-vFieldList-",40))}{unique_key_value()}"
            vFieldValue_def = replace_parameters(vFieldValue_def,local_variables())
            a_dlg_button =""
            end if
            %code%)
            ui_msg_box("test",vFieldList-"="-vFieldValue)
            --
            Support your local Search and Rescue Unit, Get Lost!

            www.westrowops.co.uk

            Comment


            • #7
              Re: Combing two Xdialog Boxes

              this and see the event (If a_dlg_button ="vfield_changed" then)

              Code:
              varC_result = ui_dlg_box("Field Selection",<<%dlg%
              {region}
              Name:| [%p=ui_get_fieldname("base_details","VFieldName");I=$a5_smart_field%.40vFieldName!vfield_changed];
              {endregion};
              
              {region}
              Entry:| [%@VFieldValue_rl_def%.40VFieldValue];
              {endregion};
              
              {line=1,0};
              {region}
              <15OK!OK> <15Cancel!CANCEL>
              {endregion};
              %dlg%,<<%code%
              If a_dlg_button ="vfield_changed" then
              	VFieldValue_rl_def = ""
              	VFieldValue_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25,2:25\",''+"+vFieldName+",left(''+"+vFieldName+",25),left(''+"+vFieldName+",25))}{}"	
              	vFieldValue_rl_def = replace_parameters(vFieldValue_rl_def,local_variables())
              	a_dlg_button =""
              end if
              %code%)
              
              end

              Comment


              • #8
                Re: Combing two Xdialog Boxes

                Another sample. Drop down box instead of radio buttons;

                Code:
                Ddwnfield_list=<<%str%
                Ati_Code
                Base
                C1
                Country
                County_Name
                District_Name
                Faa_Code
                Iata_Code
                Icao_Code
                Old_Code
                Other_Code
                Other_Name
                Place_Name
                Province_Name
                Region_Name
                User1
                unique
                %str%
                
                'you can get the field value instead of type it
                
                DIM SHARED vFieldName as c
                DIM SHARED varC_result as C
                DIM SHARED vFieldValue as C
                DIM vFieldValue_rl_def as C 
                
                varC_result = ui_dlg_box("Field Selection",<<%dlg%
                {region}
                Name:| [%p=ui_get_fieldname("base_details","VFieldName");I=$a5_smart_field%.40vFieldName];
                
                **** | apply dropdown box instead of radio;
                Name:| [.36.5vfieldName^=Ddwnfield_list!vfield_changed];
                {endregion};
                
                {region}
                Entry:| [%@VFieldValue_rl_def%.40VFieldValue];
                {endregion};
                
                {line=1,0};
                {region}
                <15OK!OK> <15Cancel!CANCEL>
                {endregion};
                %dlg%,<<%code%
                If a_dlg_button ="vfield_changed" then
                	vFieldName = vFieldName
                	VFieldValue_rl_def = ""
                	VFieldValue_rl_def = "k=base_details,{keylist_build(\"H=.05,1:25,2:25\",''+"+vFieldName+",left(''+"+vFieldName+",25),left(''+"+vFieldName+",25))}{}"	
                	vFieldValue_rl_def = replace_parameters(vFieldValue_rl_def,local_variables())
                	a_dlg_button =""
                end if
                %code%)
                
                end

                Comment


                • #9
                  Re: Combing two Xdialog Boxes

                  Ha!
                  just got there myself !!

                  thanks again for input.
                  --
                  Support your local Search and Rescue Unit, Get Lost!

                  www.westrowops.co.uk

                  Comment

                  Working...
                  X