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

Update only selected child record

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

    Update only selected child record

    Hello All,

    I am an old Alpha4V6 user and am new to Alpha5. I have downloaded V4.5 Trial to check out and show my boss how much better it is that Access.

    I have a simple one to get me started on the new addressing.

    I have a form from a set with PO_HEAD and browse table with PO_ITEMS. I can enter PO's fine. When items start coming in I want a user to:

    1. Find the PO for the items that came in
    2. Highlight the item that came in
    3. Press a button to receive that item
    4. A box appear asking for the qty received
    5. (I will add the code to check that this qty is not
    greater than the qty ordered)
    6. If qty received input is valid store this value in child table PO_ITEM.QTY_RECEIVED.
    7. This way I can keep track of how many items are on backorded.
    8. I have messed around and keep getting error messages setting the parent and child field pointer.

    This was easy to do in A4V6 just being on the child record you want by looking at the region (even showing a seperate menubar while in the region) and pressing a hot key for the item.

    I just need a jump start on the conversion from a region to the embedded browse tables. I have done alot of VB stuff and am familier with dot notations.

    By the way, it looks like A5 is going to be awesome. I am very pleased that Alpha continues to make an excellent product and has continued this message board. I was shocked to see that they have A4V7 now.

    Thanks,
    Anthony

    #2
    RE: Update only selected child record

    Anthony,

    It may help to think of your form has having two layers.

    The subsurface layer is the set of tables upon which the form is based. Using Xbasic you can write changes directly to the tables in a set, but you have to put the table in change or enter mode first. To do this one usually gets a pointer to the table, and then uses tbl.begin_enter() or tbl.begin_change(). The xbasic reference manual explains how this works. There are specific techniques that must be used to get a pointer to the parent table, and then to get a pointer to a child table. After updating the underyling table it's often necessary to repaint the form because the objects displaying the fields in your set may not automatically refresh themselves. form_object_name.refresh() or form_name.resynch() are often used to do this.

    An alternative is to write changes to the form objects on screen. this is often done by using a different syntax:

    form_object_name.text = "new value" or
    form_object_name.value = 1234.68

    This is discussed in the xbasic reference manual also. The object addressing scheme is faintly reminescent of the tree structure of a hard drive:

    If you have an object called "Lname" on a form called "Customers", you'd change it's value like this:

    :Customers:Lname.value = "New Name"

    Notice there are two colons.

    If you have an object called "ItemNo" in a child table that's displayed in a browse called "Browse1" on the "PO" form, you'd change it this way:

    :PO:Browse1:ItemNo.value = New_Value

    Notice that now there are 3 colons.

    This is discussed in the chapter on object addressing in the xbasic reference manual.

    -- tom

    Comment


      #3
      RE: Update only selected child record

      Thanks, Tom.

      Comment

      Working...
      X