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

xDialog Box

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

  • #16
    Re: xDialog Box

    Actually Ray, I did have this function and lost it with a computer crash - thanks for pointing me to where I found it originally.
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


    • #17
      Re: xDialog Box

      Cal,

      In my case, I think that Ui_msg_box() is nothing to effect about the xDialog speed and I simply inserted for checking whether my UDF get the value or not.

      I believe that Stan's point, inside of the Keylist_build(... lokup()..), made it too slow to open.

      My planning is this, (1) Limit and List a value "PlanCode_ID( Return value)" through "Finish" Table which matching the "Project_id". (2) get the "Group" value from "PlanCode" table after I select above step 1 (3)Limit and list the Vendors from vendor_Group_Lists table which is same "group" as step 2 (4)Read and write the cost from PriceBook table which is matching with "Group" and "vendor"

      My basic Problem:
      The Finish table contains "PlanCode_id(FK)", Finish_id(PK) and other fields which only belong to "Finish" table because the normalization. The PlanCode table has "PlanCode_id(Pk), Name, Series_ID(FK) and Group (which is a result value by Series_id )".
      When I made the drop down box, I am not able to see the Name field of PlanCode unless I add another "Name" field on the "Finish" table which is a redundant field. So I came as Keylist_build ( .... looup() ...).

      How do you make a drop down boxes in this case?

      Comment


      • #18
        Re: xDialog Box

        Hi,

        I changed my direction. I made some of few Map and new set tables in order to start over an same xDialog.

        I attached the code for your help. Please, tell me If I am going off road. My Intention is after I filled in 1st drop down box(vFieldcode), I want to see the available vendors by drop down box and save the result(key/Return value). The vVendorList drop down box shows only vendor name and I cannot get the return value as like Keylist_build(). So that I have to use the xdialog Event. Am I doing OK? My test on the Msgbox() is indicated as what I want.

        Code:
        dim vProjectId as c ="08-0905"
        dim vFieldCode as c ="08-0905cf1" 'Try ID
        dim vVendorList as c
        vVendorList = set.external_record_content_get("Mtr_vndrs.set",\
        "Prdctvndrs->Vendor_name","","Materialsch_id="+quote(vFieldCode))
        
        
        dim vSelectVendor as c
        
        ui_dlg_box("Give me an xdialog ",<<%dlg%
        
        Select a Vendor:| [.15vSelectVendor^=vVendorList!vSelectVendor_changed];
        
        %dlg%,<<%code%
        if a_dlg_button = "vSelectVendor_changed" then
            'open table and get the ProductVendor_id  - How???
            vPrdvndrId = set.external_record_content_get("Mtr_vndrs.set",\
        "Prdctvndrs->prdctvndr_id","","Materialsch_id="+quote(vFieldCode)+" .and. Prdctvndrs->Vendor_name="+quote(vSelectVendor))
        msgbox(vPrdvndrId)
        
            a_dlg_button=""
        end if
        %code%)

        Comment


        • #19
          Re: xDialog Box

          Is this code you are using for a button on a form where Prdctvndrs is an open table?
          There can be only one.

          Comment


          • #20
            Re: xDialog Box

            Stan,

            A button on my Estimate form. I will save it to Criteria table then using query and get the cost from price table, save the results to estimate table.

            Comment


            • #21
              Re: xDialog Box

              Try this.
              It gets the Id as well as the name in the first external content get in the form of 'Name|Id'.
              The '-' between 'Prdctvndrs->Vendor_name' and '|' trims trailing blanks in Prdctvndrs->Vendor_name
              Then initializes a property array from the list.
              The combobox displays the .name property of the array and returns the index value as numeric.
              Next the Id is retrieved using the index value.

              Code:
              dim vProjectId as c ="08-0905"
              dim vFieldCode as c ="08-0905cf1" 'Try ID
              dim vVendorList as c
              vVendorList = set.external_record_content_get("Mtr_vndrs.set",\
              "Prdctvndrs->Vendor_name-'|'+Prdctvndrs->prdctvndr_id","","Materialsch_id="+quote(vFieldCode))
              
              
              
              dim vVendorArr[line_count(vVendorList)] as P
              vVendorArr.initialize_properties("Name|Id",vVendorList)
              
              dim vSelectVendor as N
              
              ui_dlg_box("Give me an xdialog ",<<%dlg%
              
              Select a Vendor:| [.15vSelectVendor^=vVendorArr[\].Name!vSelectVendor_changed];
              
              %dlg%,<<%code%
              if a_dlg_button = "vSelectVendor_changed" then
                  
                  msgbox(""+vSelectVendor)
                  vPrdvndrId = vVendorArr[vSelectVendor].Id
                  msgbox(vPrdvndrId)
                  a_dlg_button=""
              end if
              %code%)
              Last edited by Tim Kiebert; 03-22-2011, 05:36 PM. Reason: forgot single qouotes around the pipe charachter '|'
              Tim Kiebert
              Eagle Creek Citrus
              A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

              Comment


              • #22
                Re: xDialog Box

                Tim,

                This is so cool. Thank you, Tim.

                Comment

                Working...
                X