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

success getting embedded browse to update

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

    success getting embedded browse to update

    i remember several other people mentioning problems with this one.

    i have several embedded browses, and i frequently add a record(using a childaddrecordform) or edit an existing record(using a childeditrecordform). when i do so i close the parentform!! - otherwise it just doesn't work!!! the nuisance i was having was that when i would come back to the parentform, the new record would not show up in the browse, and i would have to click on the browse and roll or arrow up or down to get the record to show up - making the end user uncomfortable that everything was cool.

    when the parentform is reopened at the onactivate event it checks the variable "cnum" to see if its value is greater than zero and if so fetches the appropriate customer.

    well, the last line in my onactivate script is parentform.resynch()

    i added the following lines and it is always showing all the records in the embedded browse in their proper order.

    parentform.resynch()
    tbl=table.current(2) 'position of the child in the set
    tbl.fetch_first()
    parentform:browse1.refresh()
    end



    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

    #2
    RE: success getting embedded browse to update

    Martin:

    This has been a thorn in my side for a long time. So I really appreciate your comments. But are you saying that the only solution is to close the form with the browse, then present the user with the data entry form, and then reopen the form with the browse?

    Gary
    Gary S. Traub, Ph.D.

    Comment


      #3
      RE: success getting embedded browse to update

      I believe so, yes. When the parentform is left open, the only way I have found to get the browse to update is to MANUALLY go to the next record and then back again. Its really no big deal. Just use a variable for your linking fields. Open the childadd or childedit setting the correct field values for an add or to fetch with in an edit. then when you come back reopening the parentform, the data is correct
      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


        #4
        RE: success getting embedded browse to update

        I have done battle here and this is the code that works for me. I do not close the parent form.
        I have a set Customer->job linked on CID (customer id). When you push a button to add a job this script runs. It uses a dialog form to get the job info and copies in the current customer records CID to the job CID, enters the date the record was entered, then does some shenanigans to make the new record show.

        It works for me.

        Vcid = CID.VALUE
        btn = :form.load("JobAdd", "DIALOG")
        :CustJob.activate()
        :CustJob:BUTTONJobAdd.activate()
        :JobAdd:Tables:JOB.enter_begin(HONOR_FIELD_RULES)
        :jobadd:tables:job.since = date()
        :JobAdd:CID.activate()
        :jobadd:tables:job.cid = Vcid
        :JobAdd:JOB0.activate()
        :JobAdd.Show()
        :JobAdd.close()

        'This code is to make the new record show in the embedded browse
        :CustJob:BROWSEJob.activate()
        :CustJob.resynch()
        :CustJob:BROWSEJob.up()
        sys_send_keys("{F5}")

        Comment


          #5
          RE: success getting embedded browse to update

          terrific - will save and try - thank's
          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