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



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

onrow doubleclick

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tom Henkel
    Re: onrow doubleclick

    Tom_B, Tom_C, and Mike,

    Thank you all for your input.

    I took a variation of Tom_B's (There are way too many Toms here) code and it produces the results I need. All I wanted to do was to make sure that when the operator double clicks on the current record I actually get the current record. Once I have the record, I can populate my dialog and let the operator have at it knowing that they are editing the record they selected.

    'Date Created: 18-Jun-2010 10:47:35 AM
    'Last Updated: 24-Jun-2010 03:38:44 PM
    'Created By  : Thomas Henkel
    'Updated By  : Thomas Henkel
    DIM vssn as C
    DIM vlname as C
    DIM hh_recno as N
    hh_recno = parentform:fambrs.current_record()
    DIM hh as P
    hh ="househol",FILE_RO_SHARED)
    vlname = hh.lname
    vssn = hh.fname
    ui_msg_box("","Last Name = "+vlname+" First Name = "+vfname)

    Leave a comment:

  • Tom Cone Jr
    Re: onrow doubleclick

    Tom_H, do you see the same results if you grab the "text" property of the two columns instead of the "value"?

    In most of my work here I use a pointer to the table being displayed in the browse rathern than try to get the field content from the browse object itself. You might try that if you're still stuck.

    I can supply an example if you wish.

    Leave a comment:

  • MikeC
    Re: onrow doubleclick

    I have an idea, but may not be correct. v9 has had an issue in some builds in regard to which record is in focus....that is, the cursor will be on one record, but another is highlighted and such stuff.

    The read only that Tom used could remedy this problem and try that if you haven't (or is something that is possible in your case). I don't think using a form (dialog) or xdialog makes any difference.

    Leave a comment:

  • Tbaker
    Re: onrow doubleclick


    I do exactly what you are doing with a browse in my inventory app. The browse is used to enter cuts and deduct from a specific roll in the inventory.

    The browse is read only. To make a change in the row the user double clicks the row and a dialog form pops up allowing them to change information, cancel the record etc.

    Here is the code that I use -

    dim inv_recno as n
    dim vptr_icuts as p
    dim global menu_hdr as c 
    menu_hdr="Edit Apartment Cuts" ' this just changes the title info to either enter or edit
    inv_recno=browse1.current_record()'get the record number of the row that was clicked
    filter="recno()="+s_quote(inv_recno)' uses it to filter the popup form to that record
    I think this is an example of what you want to do.

    edit: I used a form as a dialog, not a dialog box. So this is probably not what you need.

    Tom Baker
    Last edited by Tbaker; 06-24-2010, 01:50 PM. Reason: Just re-read your post

    Leave a comment:

  • Tom Henkel
    started a topic onrow doubleclick

    onrow doubleclick

    I've checked out the old posets on this issue and have attempted to do what was suggested, however, I still cannot get the record of the row I doubleclick on. I have a customer information form with a household browse listing that is read only. I would like for the user to double click on a row in the browse so that I can pop up a dialog box to allow them to modify the record they click on. The onrowdoubleclick event ALWAYS gives me the first person in the browse.

    DIM vssn as C
    DIM vlname as C
    vssn = parentform:fambrs:ssn.value
    vlname = parentform:fambrs:last_name.value
    ui_msg_box("","Last Name = "+parent:fambrs:last_name.value+" First Name = "+parent:fambrs:first_name.value)
    results in thumbnail:

    any suggestions would be appreciated...