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

<Browse>.HOME() works one place but not another

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

  • <Browse>.HOME() works one place but not another

    Hi all

    I think this is a scope issue or a where the focus is issue but I cant see it.

    This is my code attached to events on a browse.

    it does a simple check on the existence of a data Pair in a table and then what gets done with that data.

    I have got the detection going and there are some choices that get made.

    when i say No to adding the record I want the focus to return to the first column of the browse using


    Parentform:CONTROL_BROWSE1.home()

    it doesn't work straight after the no selection

    but does at the end of the function which of course is the wrong place.

    please tell me the obvious.

    Code:
    FUNCTION Product_ID_onchange as v ()
    
    DIM GLOBAL VProd_ID AS n
    dim tbl as P
    dim qry as P
    dim nrecs as N
    	
    VProd_ID = CONTROL_BROWSE1.Product_id.value
    
    'ui_msg_box("On Change Event for Browse. Browse name is: ",this.name() + crlf()+ "Product ID  " + VProd_ID + crlf() + "Customer ID" + VCust_ID)
    
    
    tbl = table.open("cust_prod_join")
    query.description = "Data_Pair_exist"
    query_order = ""
    query_filter = "Product_ID = VAR->VProd_ID .and. Customer_ID = VAR-> VCust_ID"
    query_flags = ""
    qry = tbl.query_create(query_flags, query_filter, query_order)
    nrecs = qry.records_get()
    IF (nrecs = 0) then
        qry.drop()
        responce = ui_msg_box("No Data Pair","This is a new product for this Customer. Do you want to add it?",UI_YES_NO)
        if responce = UI_YES_SELECTED then
        	ui_msg_box("YES","YES")
        elseif responce = UI_NO_SELECTED then
        	
        	'ui_msg_box("NO","NO")
        	Parentform:CONTROL_BROWSE1.home()   'This doesnt work
        end if
            	
        query.order = ""
        query.filter = ""
        tbl.close()
        
        END
    end if
    
    'ui_msg_box("Data Pair Exists","This product already is made for this customer. No further action required",UI_INFORMATION_SYMBOL)
    
    tbl.close()
    
    Parentform:CONTROL_BROWSE1.home()  'this does work
    
    END FUNCTION

    regards
    Why did I ever say yes?

  • #2
    Re: &lt;Browse&gt;.HOME() works one place but not another

    You don't show where cust_id is established and dimmed and what type it is. Likely it is global but the filter should be (to expose the variables)

    query_filter = "Product_ID = "+VAR->VProd_ID+" .and. Customer_ID = "+VAR-> VCust_ID

    if cust_id is numeric

    query_filter = "Product_ID = "+VAR->VProd_ID+" .and. Customer_ID = "+quote(VAR-> VCust_ID)

    if it is character.
    There can be only one.

    Comment


    • #3
      Re: &lt;Browse&gt;.HOME() works one place but not another

      The VCust_ID is a global variable that is given a numerical value as the form opens.

      Just to make sure I also set the variable in the script.

      What's happening is that the first

      Parentform:CONTROL_BROWSE1.home()

      function is not causing the cursor/focus to go to the first column of the browse. it stays in the column that I selected.

      but the second one does
      Why did I ever say yes?

      Comment


      • #4
        Re: &lt;Browse&gt;.HOME() works one place but not another

        Maybe put parentform:control_browse1.activate() immediately prior to the .home?
        There can be only one.

        Comment


        • #5
          Re: &lt;Browse&gt;.HOME() works one place but not another

          Don't ask me why but

          replace the

          Parentform:CONTROL_BROWSE1.home()

          with (both lines)

          sys_send_keys("{home}")
          sys_send_keys("{home}")
          There can be only one.

          Comment


          • #6
            Re: &lt;Browse&gt;.HOME() works one place but not another

            Thanks for that. wood for trees stuff.
            Why did I ever say yes?

            Comment


            • #7
              Re: &lt;Browse&gt;.HOME() works one place but not another

              Seems to me that Parentform:CONTROL_BROWSE1.home() should work but I don't keep after something very long if I can find an alternative.
              There can be only one.

              Comment


              • #8
                Re: &lt;Browse&gt;.HOME() works one place but not another

                The tricky thing is knowing what those alternatives are. And I like to think that I have done some good research before asking the questions I do.

                one day it may be my turn to contribute as well as being helped.
                Why did I ever say yes?

                Comment

                Working...
                X