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

Detect "Enter" on embedded Browse

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

    Detect "Enter" on embedded Browse

    Is there a way to detect when an embedded browse has a new record entered? What I want is to NOT enter child records in the browse, but rather pop up a dialog form to enter data instead.

    I can restrict the browse Entry property and put a button on the form, but I was wondering if it was possible to simply intercept the event with xbasic...

    #2
    RE: Detect

    Steve, Not sure exactly what you are looking for but you can use count() to show number of records when you start and then compare number of records when finished. If it is more, then record(s) were entered.
    Example:
    count(your_table->your_field,GRP->your_header_table)

    You can also check the table mode using the following and inserting your scripting in place of the message boxes:

    tbl = table.current() 'or the table in question?
    IF tbl.mode_get() = 1 THEN
    ui_msg_box ("Mode", "Change mode")
    ELSEIF tbl.mode_get() = 2 THEN
    ui_msg_box ("Mode", "Enter mode")
    ELSE
    ui_msg_box ("Mode", "View mode")
    END IF
    If the table goes into the ENTER mode you could intercept at that point.

    Comment


      #3
      RE: Detect

      Why not make the browse read only and restrict entry and changes, then put the code to open the dialog form in the On Row Double Click event ... if it's not used for anything else. You could have it branch so that the user has choices depending on circumstances: "Edit this record?", "Enter a New Record?", "Delete this Record?", that sort of thing.

      Finian
      Finian

      Comment


        #4
        RE: Detect

        Yeah - but a "&New Record" button is just as easy. I am so used to dealing with Alpha Five in the raw and I am NOT used to packaging interfaces. I want to use a form for data entry as I can do more friendly interfaces. I couldn't see any direct method to capture the OnEnter event from the embedded browse, but that didn't mean there wasn't one...

        Thank you..

        Comment


          #5
          RE: Detect

          Finian's idea looks good, but if the user goes to the last record and then [down arrow]s to the next record I don't think your script would get triggered. And if there are no records in the browse (due to linking index filter) you might be stuck in entry mode.

          Can you use a onEnter() event for the browse, and have the event send a "cancel" string and then open a dialog, get the info from the dialog, and then do the enter in the same script? (Hmm. That might create an infinite re-entrant onEnter() trigger. Maybe the first part of the onEnter() script would check to see if the dialog is open and branch around re-opening the dialog.)

          Perhaps the easiest way would be to restrict entry on the browse and use a button to open the dialog and do the entry in xbasic as you mentioned. Maybe start with that and play with the above method when you have time (as if any of use ever have any time to play with code any more.)

          Comment


            #6
            RE: Detect

            thank's to my early mentor, Tom Cone, I only let the user enter records in a browse if its very simple, like a phone number - otherwise I use a childaddform via rowdoubleclick - this makes it much easier to have a lot of background code for each field, and makes it much easier to display as many fields as I want.
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment

            Working...
            X