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

Browse Question

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

  • Browse Question

    I have an embedded browse on Order Entry Form.
    The fields are Style#, Qty, description and price.
    The style number is chosen by a lookup table and completes the other fields.
    I would like to use the "enter" key to start a new record after choosing the QTY of the item. I could use a skip function, However I need to change the description or price from time to time.

    Any Solutions?

    thanks

  • #2
    Re: Browse Question

    Hi Jeff,

    Have a look at AlphaSports, that works just the way you describe.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


    • #3
      Re: Browse Question

      Thanks for the response. Actually, in Alpha sports you have to enter to the last line before it drops down to a new record.
      I want it to drop down after entering the QTY.

      Comment


      • #4
        Re: Browse Question

        Never tried it with a browse but can you use the forms onkey event. Check to see if the browse qty column is the current active object when the enter key is pressed, if so start new record.

        Geoff

        Comment


        • #5
          Re: Browse Question

          Try the following code in the form onkey event.

          Code:
          active_object= current_object()
          active_object=right(active_object, 4)
          
          if sys_key_down("ENTER") then
          	if  active_object = ":Qty" then 
          		topparent:Browse1.new_record()
          	    else
          	end if
          		
          end if

          Comment


          • #6
            Re: Browse Question

            What would happen if Qty was the last column in the browse?
            Regards
            Keith Hubert
            Alpha Guild Member
            London.
            KHDB Management Systems
            Skype = keith.hubert


            For your day-to-day Needs, you Need an Alpha Database!

            Comment


            • #7
              Re: Browse Question

              The following does not work. Any other suggestions?
              active_object= current_object()
              active_object=right(active_object, 4)

              if sys_key_down("ENTER") then
              if active_object = ":Qty" then
              topparent:Browse1.new_record()
              else
              end if

              end if

              Comment


              • #8
                Re: Browse Question

                Jeff

                Try this in the onkey event

                Code:
                IF a_user.key.value = "{ENTER}" .and. browse1.active()="Qty" THEN
                	
                    a_user.key.handled = .T.
                
                    IF a_user.key.event = "down" THEN
                		:form1:browse1.Commit()
                         :form1:browse1.new_record()
                
                    END IF
                
                END IF
                You would have to change :browse1.active() to whatever you named your browse (maybe browse1) and then also change :form1:browse1 to whatever you called the form and the browse.

                Tom

                Comment


                • #9
                  Re: Browse Question

                  Jeff,

                  I think there is a timing issue with my script which causes it to start a new record not only for the qty column but the one prior to it as well.

                  Tom's script works (and I will be adding it to my useful code list) but I would use the alias topparent or this instead of the explicit form name. That way if the form is opened more than once it should still work.

                  Code:
                  IF a_user.key.value = "{ENTER}" .and. browse1.active()="Qty" THEN
                  	
                      a_user.key.handled = .T.
                  
                      IF a_user.key.event = "down" THEN
                         [COLOR="Red"]topparent[/COLOR]:browse1.Commit()
                         [COLOR="Red"]topparent[/COLOR]:browse1.new_record()
                  
                      END IF
                  
                  END IF
                  or

                  Code:
                  [CODE]IF a_user.key.value = "{ENTER}" .and. browse1.active()="Qty" THEN
                  	
                      a_user.key.handled = .T.
                  
                      IF a_user.key.event = "down" THEN
                         [COLOR="Red"]this[/COLOR].browse1.Commit()
                         [COLOR="Red"]this[/COLOR].browse1.new_record()
                  
                      END IF
                  
                  END IF
                  [/CODE]
                  I would be interested in any thoughts which of the two relative addresses is the most appropriate. Both seem to work but I wonder if there is a reason to use one rather than the other. Appreciate anyones thoughts regarding these suggestions as I don't want to lead Jeff down the wrong route.

                  I have attached an example if it helps.

                  I experimented further and it seems to work without using the form name. Just
                  Code:
                  	browse1.Commit()
                         browse1.new_record()
                  What would be best practice?

                  Comment

                  Working...
                  X