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 with fillable/changeable field

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

    #16
    Re: xdialog with fillab;e/changeable field

    In the initial formative period of learning A5, so may remarks were against using standalone browse - I followed and just built them inside forms.
    I lost out on some possibilites it seems.
    Originally posted by Al Buchholz View Post
    It's easier to merge multiple browses on a single xdialog without having a set that ties it together... - ie dashboard..
    Wow. Now THAT is very intriguing - from one, switch to another.. sort of? by calling another UDF or goto within one code file?

    Originally posted by Al Buchholz View Post
    Functions carry forward from the browse into the code for the xdialog. Change functionality in the browse and then move the code to the xdialog. It's not a build an xdialog and point to a browse. But you can see that from the code that is built.
    Good insights. Thanks for a very informative reply ( so far)

    Comment


      #17
      Re: xdialog with fillab;e/changeable field

      Originally posted by Ray in Capetown View Post
      Wow. Now THAT is very intriguing - from one, switch to another.. sort of? by calling another UDF or goto within one code file?
      With a little manual combining of the code generated, multiple browses can be on the same xdialog without the overall set combing the 2 browses..
      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


        #18
        Re: xdialog with fillab;e/changeable field

        yes ray, i'm writing all of the logic now. i need to allow for double blind entry of the lot number, write the code that checks and validates the entry. based on the entry, i may have to display another xdialog to get managerial approval to continue. once the entry is validated, i show another xdialog that allows the user to print the number of barcoded labels needed and then write the data to a table. from there, a sql routine imports the data into the sap accounting system. all of this checking /verifying has to do with haacp.

        i've changed some of what i had in the example i posted, because it was left over from a method i was using while developing the xdialog and all of the variables.
        i tried to put enough comments in it so what i was doing could hopefully be deciphered.

        Comment


          #19
          Re: xdialog with fillable/changeable field

          since this application is about to go live, I figured i'd post a simple pdf help type file of what I've done. if anyone has any questions / comment, please feel free. (if I can get the pdf uploaded)
          can't upload it for some reason, so i'll try a link to skydrive
          http://tinyurl.com/k7flhtr
          Attached Files
          Last edited by gkeramidas; 08-18-2013, 10:16 AM.

          Comment


            #20
            Re: xdialog with fillable/changeable field

            Note to Al , I am referring to post 15
            I want to thank you for that particular post. It had a major influence - a game changer.

            I now can, (just one example) pop up a modal browse XDlg -with specific fields editable if necessary- that reference records relevant to the current form browse item elsewhere in the table. Works like a drill-up as opposed to drill down. ie. What else like this item is doing what elsewhere AND edit if outdated?

            I haven't yet tried to combine code from multiple browses.
            Last edited by Ray in Capetown; 08-18-2013, 04:36 AM.

            Comment


              #21
              Re: xdialog with fillable/changeable field

              Originally posted by Ray in Capetown View Post
              Note to Al , I am referring to post 15
              I want to thank you for that particular post. It had a major influence - a game changer.
              Ray

              You're welcome.

              I don't remember how I found it. I know I was looking for a way to build more dashboard like forms.

              Probably 'hunt and click' to see what options are available....

              When combining browses, the area in red (per image attached) allows you to generate code with unique names and attributes.

              The xbasic code for browse events is included so the browse works just like a stand alone....

              So Browse1 and Browse2 can be completely diverse data but still be on the same form (although it is an xdialog form).

              Or with a xbasic watch, you can have a variable control the fetching of records. When one browse changes to another customer, you can have the second browse show that customer's details. So you have a set without the definition of the set. That allows a linkage that is more controllable than a set.


              CLICK HERE FOR IMAGE..
              Upload to msgboard didn't work....
              Attached Files
              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


                #22
                Re: xdialog with fillable/changeable field

                Gary,

                How did you write the SAVE event on your last code( "po_test")?

                Comment


                  #23
                  Re: xdialog with fillable/changeable field

                  well, it changed quite a bit since that post. that was to show how I used variable number of line items to create the xdialog.
                  I basically save the data entered when the item number button is clicked. right now it goes to a temporary table, but i'm rewriting it to store it all in an array, and then just post the data when the user clicks on Post PO. (not on the potest form).

                  if tat's not what you mean, just post back.

                  Comment


                    #24
                    Re: xdialog with fillable/changeable field

                    Gary,

                    I basically save the data entered when the item number button is clicked.
                    Thank you and - so I have to click 20 times for saving the records on the buttons If I have 20 lines.

                    question

                    How can I read and get the variable fields the lines which inside of the DLG_Box ?

                    I mean, read and converting to line listing value. I have the sample values at dlg_box() as

                    and want to convert as like this

                    result_list =<<%result%
                    vItm1 ="a" ,vgp11 ="1a", vgp12 ="2a" , vgp13 ="3a"
                    vItm2 ="b", vgp21 ="b1" , vgp22 ="b2" , vgp23 ="b3"
                    vItm3 ="c" ,vgp31 ="1c" , vgp32 ="2c" , vgp33 ="3c"
                    %Result%
                    See Sample code

                    Code:
                    '
                    DIM  vItm1 as C
                    DIM  vgp1 as C
                    DIM  vgp2 as C
                    DIM  vgp3 as C
                    
                    'Set the temp value
                    vItm1 ="a"
                    vItm2 ="b"
                    vItm3 ="c"
                    vgp11 ="1a"
                    vgp12 ="2a"
                    vgp13 ="3a"
                    vgp21 ="b1"
                    vgp22 ="b2"
                    vgp23 ="b3"
                    vgp31 ="1c"
                    vgp32 ="2c"
                    vgp33 ="3c"
                     
                    ok_button_label = "&OK"
                    cancel_button_label = "&Cancel"
                    
                    DIM  varC_result as C
                    'varC_result = ui_dlg_box("group line",<<%dlg%
                    ui_Modeless_dlg_box("group line",<<%dlg%
                    {region}
                    Item:|  Field1:| Field 2:| Field 3:| ;
                    [.40vItm1]|[.10vgp11]|[.10vgp12]|[.10vgp13];
                    [.40vItm2]|[.10vgp21]|[.10vgp22]|[.10vgp23];
                    [.40vItm3]|[.10vgp31]|[.10vgp32]|[.10vgp33];
                    
                    {comment and more fields are here}
                    
                    {endregion};
                    {line=1,0};
                    {region}
                    <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
                    {endregion};
                    %dlg%,<<%code%
                    If a_dlg_button ="ok" then
                        a_dlg_button =""
                        'How do I know the current Line?
                        'How to convert to list (get all records) on this dlg variable fields?
                        nCount = *count("group Line")
                        msgbox(str(ncount)) 'result - none    
                        showvar("group Line","test") 'result - none 
                        
                        'if ui_dlg_eval_valid("group line","vitm1") then
                    		'If it does exist, use UI_DLG_EVAL()to read it and display it in a message box.
                    		ui_msg_box("Show the Value","" + ui_dlg_eval("group line","vItm1 +\";\"+ vGp11"))
                        'else
                       '     ui_msg_box("Error","Dialog 'Test' is not open.")
                        'end if 
                    end if
                    if a_dlg_button = "cancel" then
                        ui_modeless_dlg_close("group line")
                    end if
                    
                    %code%)
                    Any Idea?

                    Comment


                      #25
                      Re: xdialog with fillable/changeable field

                      well, the reason I have a button for each line is each item that's received has to be individually verified and a variable number of labels printed, it's not always a value in the form.
                      I dim the number variables based on a line_count() of the values, so I know how many there are of each one.
                      right now, i'm using the size of an array to get the variables I need dimmed:
                      Code:
                      for x = 0 to PO_itmArr.size() -1 ' create variables to be dimmed
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x)) + " as c" + crlf() ' Item Number
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x)) +  "DE as c" + crlf() ' A Description
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x)) + "QO as n" + crlf() ' B Qty Order
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x)) + "OQO as n" + crlf() ' B Original Qty Order
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x)) +  "QR as n" + crlf() ' C Qty Rec
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x)) +  "QF as n" + crlf() ' d Qty Ref
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x))  + "LN as c" + crlf()' E lot #
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x))  + "Ver as c" + crlf()' F Inspected
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x))  + "Rea as c" + crlf()'  Reason
                      	cmd = cmd + "dim Line_Item" + alltrim(str(x))  + "Note as c" + crlf()'  Notes
                      	cmd = cmd + "dim en_dis" +alltrim(str(x)) + " as l" + crlf() ' enable / disable button
                      next
                      by the size of the array, i would know the name of all of the variables and would be able to loop through them all to save a record.

                      this is what the variables would be if I had 2 items to process:
                      Code:
                      dim Line_Item0 as c
                      dim Line_Item0DE as c
                      dim Line_Item0QO as n
                      dim Line_Item0OQO as n
                      dim Line_Item0QR as n
                      dim Line_Item0QF as n
                      dim Line_Item0LN as c
                      dim Line_Item0Ver as c
                      dim Line_Item0Rea as c
                      dim Line_Item0Note as c
                      dim en_dis0 as l
                      dim Line_Item1 as c
                      dim Line_Item1DE as c
                      dim Line_Item1QO as n
                      dim Line_Item1OQO as n
                      dim Line_Item1QR as n
                      dim Line_Item1QF as n
                      dim Line_Item1LN as c
                      dim Line_Item1Ver as c
                      dim Line_Item1Rea as c
                      dim Line_Item1Note as c
                      dim en_dis1 as l
                      knowing this, I know what the value of any give variable would be.
                      if this doesn't help, try to give me something I can run and see what you're trying to accomplish.

                      Comment


                        #26
                        Re: xdialog with fillable/changeable field

                        Gary,

                        I can read and get the value from Inside of the dlg_box() with this code but I could not figure out crlf() list yet.
                        Do you have any idea How to make the List
                        Code:
                        Line one + crlf() 
                        Line two + crlf() 
                        Line three + crlf()
                        Code:
                        'Replaced the Event from the previous sample code
                        If a_dlg_button ="ok" then
                            a_dlg_button =""
                            dim i as n
                            dim k as n
                            dim vline as c
                            for i = 1 to 3
                            	if eval("vitm"+i)<>"" then
                            	    ui_msg_box("found","for "+"vItm"+i+" value as "+[COLOR="#0000FF"][SIZE=3]ui_dlg_eval("group line","vItm" +i) [/SIZE][/COLOR])
                            	   [B][COLOR="#FF0000"][SIZE=3] vline = eval("vitm"+i) +";"[/SIZE][/COLOR][/B]
                            	    for k = 1 to 3
                            	    	if eval("vgp"+i+k)<>"" then
                            	    		 ui_msg_box("found line","for "+"vGp"+i+k+" value as "+ui_dlg_eval("group line","vgp"+i+k) )
                            	    		[B][COLOR="#FF0000"] [SIZE=3]vline = vline+	eval("vgp"+i+k)+";" [/SIZE][/COLOR][/B]
                        '** I tried this, moved up and down and added  " crlf() " and deleted ,  
                            	    	end if		
                            	    next	
                            	end if
                            next	
                            showvar(vline)
                        end if

                        Comment


                          #27
                          Re: xdialog with fillable/changeable field

                          sorry, I'm not sure what you're truing to do. maybe you can post a before and after to give us an idea.

                          Comment

                          Working...
                          X