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

Calculating child record ID based on parent record

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

  • Calculating child record ID based on parent record

    I am trying to create either a form or a table calculated field that will auto increment to the next available sub record ID (002). The form is a job order detail of its parent where customer header and site location information is entered. The parent form has an auto increment record ID. This is set to a local variable and entered into the child form with the use an action script on a push button. At that point the detail subform is displayed. I would like to create a script that fills the sub record field on the form with "001" if this is the first subrecord for the current record or increments by one from the last sub record for the current record. I hope someone has figured this out befor me but I have not found a good match for my situation yet.

  • #2
    RE: Calculating child record ID based on parent re

    We do something similar, but I don't (yet) autofil the field. We need to set up Activity # for work activity. Rather than putting the oneous on the data entry operator to track which # is next. I just fetch_last within the set, and display the Next available number. Using the db_current() you can specify which db_current within a set you are talking about. This is ver 1 code, but it shouldn't be very hard to convert to ver 4.


    '***** test for update mode
    if db_mode_get(db_current(2)) > 0 then
    sys_send_keys("{F9}")
    ui_msg_box("Warning", "Already in data entry mode.", 48)
    else
    ' ***** get the last child record in a two table set *********
    fetch_last(db_current(2))
    dim shared act as N
    ' ***** increment activity # and display.
    act = workact->actno+1
    ' ***** Here, instead of displaying the #, you would want to place some code 'to place the incremental value into the proper field.
    ui_msg_box("Next activity ",str(act))
    menu_run("Records/Enter")
    end if



    Tom

    Comment


    • #3
      RE: Calculating child record ID based on parent re

      One of the earliest articles posted at www.learn alpha.com is entitled "Numbering Browse Lines" and, while it doesn't exactly match your situation, it's close enough to get you going in the right direction.

      Finian
      Finian

      Comment


      • #4
        RE: Calculating child record ID based on parent re

        Here is the default expression I use to "auto-increment" the task numbers (in child table) associated with a project. It's been in use for years and works great. You should be able to adapt it to your situation.

        The first task number for project "BIGPROJ" would be: BIGPROJ-001.

        TRIM( PROJ_NUMB ) +"-"+ RIGHT( TRIM( STR( VAL( RIGHT( TRIM( DBMAX( "tasks.dbf", "proj_numb", PROJ_NUMB, "tasknumb") ), 3) ) + 1001) ), 3)

        Since the tables are linked by the PROJ_NUMB, this value is always available to the expression.

        Comment


        • #5
          RE: Calculating child record ID based on parent re

          Thanks everyone!, I'll go through all of this information and see how I can adapt it to my situation. It looks promising.

          Mike

          Comment

          Working...
          X