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

Fetching in an Embedded Browse

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

    Fetching in an Embedded Browse

    I have the need to do the following:

    Open a form with an embedded browse, scroll to a specific record in that browse, close the form and then re-open the form with the browse showing the previously selected record. Could I capture the record number of the browse and then fetch to that record when I open the form? What would the code look like if I did this with a button?

    Thank, Don

    #2
    Re: Fetching in an Embedded Browse

    this example presumes you are working on a table or set called customers, where the parent table is named customers
    the key field in customers is custno, for a character based customer number

    in an autoexec script dim 2 global variables
    dim global rnum as n
    dim global lastcust as c

    1. FORM BASED ON A SET: if the "browse" is based on the parent table, and each record has a unique key field, like say 'custno', and the parent table has a simple index based on that field

    ----- when you close that form, say var->lastcustno=parentform:custno.value
    ----- when you open the form, at the oninit event for the form put
    if var->lastcust > ""
    parentform.index_set("custno")
    parentform.find(var->lastcust)
    var->lastcust=""
    end if

    2. FORM BASED ON A TABLE: same as above

    optionally you could use the variable rnum to store the record number and say
    ---at close
    t=table.current()
    var->rnum=t.recno()
    ---at oninit
    if rnum > 0
    parentform.index_set("")
    parentform.find(var->rnum)
    rnum=0
    end if

    you could also save these as "super variables saved in the registry of the local workstation" and set them when the app opens
    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


      #3
      Re: Fetching in an Embedded Browse

      Martin - I was not clear on my needs. My form is based on a one to many set and has an embedded browse for the child records. The form has a base query that is set by a variable so that when I open the form there is only one parent record showing and all the related children in the browse. I want to scroll down to a particular child record in the embedded browse and then be able to close the form, re-open it (it will open to the same parent record) but have the embedded browse fetch to the the record I was on when I closed the form.

      Thanks,Don

      Comment


        #4
        Re: Fetching in an Embedded Browse

        Hi Don,
        To see this work, place a key field from your browse record outside the browse on the form. Dim a global variable and place it on the form. In a double click event for the browse set the variable to the value of the form field. The variable will now be set to that value even if you close the form.

        This is the script for a button to locate the record in the browse when you reopen to the SAME parent record:

        In this example I am using a set to show employee loan transactions so my key field is LT_ID and the variable is GET_LTID

        Code:
         
        dim global get_ltid as c
        dim chld as p
        dim n as n = 0
        dim rec as n = 0
        chld = browse1.table_get()
        chld.order("LT_ID")
        chld.fetch_first()
        while .not. chld.fetch_eof()
         if chld.lt_id = get_ltid then
             n = n+1
             rec = chld.recno()
         end if
         chld.fetch_next()
        end while
        if n <> 0 then
         chld.fetch_goto(rec)
        end if
        browse1.resynch()
        My normal doubleclick event for the browse opens up the loan transaction record for editing - so I don't have to close the parent form. You didn't mention why you need to close and reopen the form, but zoom_to_record() accomplished what I needed. The key field from the child table needn't appear in the browse itself. And you can hide the field from displaying on the form by making it look invisible or by placing it on a conditional object page that never shows.

        I displayed the fields in design mode just for the snapshot.
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment

        Working...
        X