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

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

    xDialog

    I have attached the Zip files. Please, open the my ChangeOrders form, then click on Add item and Hour button.
    (1) When you select the Add Item Button, Radio selection displays.
    (2) Select a Labor radio button. An xDialog form will display. I call this "Labor Part Code xDialog".
    (3) I'd like to enter the work hour on the Quantity field so I can calculate the labor cost by Hour. But, within this form (Labor Part Code xDialog) the rates do not automatically adjust by hour.
    (4) When you select the Hour button, a form displays. This form is meant to calculate the hourly work rate by given Area (sq Ft). I called this form "Labor Calculator xDialog".

    My question is
    How to combine these two xDialogs (my sample A and B) form in one place?

    #2
    Re: xDialog

    One is an xdialog, the other is a form. I don't see a "sample A and B". Your description is much too general (at least for me) to follow what it is you are trying to do. Suggest clear, exact, step by step instructions, so that we may understand what it is you are trying to do.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: xDialog

      Hi Peter,
      After I choose the labor Radio button, I like to see "Labor Calculator (A)" and "Labor Part Code (B)" in one page. So I will figure the Labor Hour with other related fields on one screen.
      I'd like enter the work hour only on the QTY Field when I figure for labor items. I do not want to open the Labor Calculator" in order to figure the hour then open new "labor Part Code", enter the same data again.

      Comment


        #4
        Re: xDialog

        Jonkoh, I looked at your sample and have a couple of questions. You have a xDialog action script producing one of your "screens" and a form based off of the menu.dbf table as the other screen. Data elements XYZ are on one form and data elements ABC are on the other form.

        Assumption:
        All data elements XYZ and ABC need to be on the same "screen" because they are related?

        It appears you already have a very good start on both ways of creating the "screen". Are you wanting a form or a xDialog as the "screen".

        Are you having any issues with deciding on which type of "Screen" to use or any issues on completing the layout of the "Screen"?
        Andrew

        Comment


          #5
          Re: xDialog

          John,

          I think Andy has said what I was going to say. Do you want xdialog or forms? xdialog is faster to load then a form, but less flexible in terms of design (or, at least more difficult to work with - as you, no doubt, are aware, xdialog script is terse and cryptic). Suggest you put everything on one form. You can use variables where needed on a form just like xdialog (which is basically all variables).
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: xDialog

            Andy and Peter,
            I did not mean to add those xdialog forms in one screen(form). I mean the steps or procedure of my scenario.
            I'd like to work with Action Script xDialogBox instead of the stand alone(?) Xdialog form.
            This is what I want to do on here.
            First, I want to figure the Work Hour base on square foot of area.
            (1) SQFT divides by day labor production = work days
            (2) work days x 8 hour = labor hour
            (3) Day labor production(field) comes from a Labor Table
            Now I know how many hour will take to do this job.
            second, I enter the Hour with labor Part ID which I already entered.
            (a) Work Hour x Labor hourly rate = labor cost.
            (b) Click OK button and save to table.

            My problem is, If I add those Labor Calculate procedure(fields) in the Labor Part Code form, I should know the work hour, before click on OK button, then enter the quantity of work hour, save file.
            Example: SqFt / Production (lookup from table) x 8hr = **6.25 hr**
            How can I display the result 6.25hr on my Labor Part Code xDialog form before enter "OK" button?
            I like to change the result, something like 7hr or 8hr, when I enter on QTY field.

            Comment


              #7
              Re: xDialog

              I see your Labor Part Code xdialog. Not sure where you do your calcs though. Are you trying to fill the quantity variable (xlbrqty)?

              Where ever you do your original calc, put this in the code:

              DIM SHARED xlbrqty as N
              xlbrqty = your calc value

              Then your xdialog will display the value when it loads.
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #8
                Re: xDialog

                Peter,
                Thank you but I think you did not understand still. I will make the xDialogBox form and attach latter.
                Thank you again.
                Have a great weekend.

                Comment


                  #9
                  Re: xDialog

                  John,
                  I think a big issue is terminology here. Basically you have either a Form or you have an xDialog [Box]. You have used the terms "xDialog form", "xDialogBox form", "Action Script xDialogBox", "stand alone(?) Xdialog form", "page", "screen", "screen(form)", and last but not least, "form".

                  Although some of these terms can be used in a generic way, some are just confusing as all get out. I suggest using only the two I mentioned first...xDialog and Form which I believe to be what you are actually using---but make absolutely certain you are using the appropriate term when making a reference.
                  Mike
                  __________________________________________
                  It is only when we forget all our learning that we begin to know.
                  It's not what you look at that matters, it's what you see.
                  Henry David Thoreau
                  __________________________________________



                  Comment


                    #10
                    Re: xDialog

                    Hi Mike,
                    Thank you for your comment. I will keep in my mind and try to use the right terminology.
                    I changed the the xDialog form for your help. I added the few variable fields in the previous xDialog ( Labor Part code) and changed the title name to Labor Cost. I also added the numbers on the each fields.
                    This is what I want to do and asked about.
                    Please, open the ChangeOrders form --> click on Add Item button --> Select a Labor Radio button --> "OK" --> Open the Labor Cost form. Now, I want to enter the data into Line (1), (2), (3), (4) and (5) then I like to see the result on line (6), (7), (8) before enter the "OK" button.
                    The line (9) and (10) will be added by user after see the above results.
                    "OK" button for save it and write to Browse.
                    My Question is How can I make
                    (a) Lookup command -- Line (6) bring the information from DBF which match with line (5) labor code.
                    (b) calculate commands -- line (7) and line (8)

                    Do I need Two of xDialog forms? If it does, how can I display the result fields on 2nd xdialog form?
                    or it is impossible within xDialog form.

                    Comment


                      #11
                      Re: xDialog

                      I hope this is what you want John, I had to convert some of your variable to numeric for calc purposes, convert the labor xdialog to xbasic, and add the following code in the code section of the xdialog
                      Code:
                      if a_dlg_button ="vlbrcode_changed" then
                          a_dlg_button=""
                          
                      	vProduction=lookupn("F",vlbrCode,"Production","laborrate","Lbrrate_Id")
                      	vLbrDay=round(vAreaQTY/vProduction,2)
                      	vLbrHr=round(vLbrDay*8,2)
                      end if
                      Then I copied it all over to a script and saved it on the code tab for easier editing.

                      Hope I have understood what you wanted

                      Comment


                        #12
                        Re: xDialog

                        Lance,
                        Waoooo!!!

                        Thank you. That is what I want and must know the tip.

                        Comment


                          #13
                          Re: xDialog

                          let action scripting be your foundation, then when it all looks like what you want, convert to xbasic and start adding the nuts and bolts!

                          Comment

                          Working...
                          X