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

Append and Line Number

  • Filter
  • Time
  • Show
Clear All
new posts

  • Append and Line Number


    I am using the "Numbering browse lines" by Peter Wayne on the OnSaveRecord events for "Line_no" field. It works fine for as standard action case.

    I added the Append Operation on same Form. Whenever I executed the Append Operation, My "Line_no" field did not display the "value" at all. If I changed a value on any fields then the "Line_no" field is displayed the line number value.

    Did I missing some of the Refresh or Save_record scripts in the "numbering browse lines"?

  • #2
    Re: Append and Line Number

    I just found this under Run_total() in the Help and adapted it to work with count() & Run_Count()

    Create a calculated field to display in the browse with this format
    ln_no = if(eof(tablename),count(field),run_count(field,GRP->Grand,GRP->dept))

    if you don't use the eof() the last record will have the same number as the next to last.

    My table:

    ln_no = if(eof("dept"),count("dept_id"),run_count("dept_id",GRP->Grand,GRP->dept))

    In your case with a set:

    ln_no = if(eof("inv_line_items"),count("inv_no"),run_count("inv_no",GRP->Inv_Hdr,GRP->Inv_line_items))

    Now that's assuming you don't need to have this line number hard coded into the table! Since it now a calculated field in the form and not a table field your append should not affect the line numbering at all - and you can still add a record to the browse the standard way. Plus you can now get rid of the OnSaveRecord & OnDeleteRecord events.
    Last edited by MoGrace; 06-28-2010, 03:27 PM.

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


    • #3
      Re: Append and Line Number


      Thank you.
      I think
      xLineNo = run_count(Estindirect->Estimate_Id,GRP->estimate,GRP->estindirect)
      is just fine in order to get the line number only but this is only Form Level and calculated value. I mean without eof() and count().

      If I want to use this function (as your style) on the table level , I got the error as
      Cannot use function in this context.
      Probably, Run_count() function may not able to use on Table level.


      • #4
        Re: Append and Line Number


        i think robin wants you to create a calculated field in form level.


        • #5
          Re: Append and Line Number

          Originally posted by fddizon View Post

          i think robin wants you to create a calculated field in form level.
          Yes it is a calculated field defined at the form level and placed in the browse - I thought I put a picture! oops. The eof() is probably what made it seem like some sort of table function.

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


          • #6
            Re: Append and Line Number


            Thank you

            Just add a (Calculated Value) line number is fine but In my case, some of my Table's primary Key Value was set as the "foreign key + Line_no".

            Some of my child table get the data from xDialog and used the <tbl>.Enter_begin() or <tbl>.change_begin() for saving record. The "numbering..." scripts is not working with the xDialog case neither.

            That is why I am trying to use "Numbering.." scripts.


            • #7
              Re: Append and Line Number

              I see your dilemma. Are you appending new records to a parent where existing records are already linked? Because you could search for those records first and get the last line number and set a variable to use in a calculation for that field in your append. So if records found = 0 then you can start at 1. In the append just pass a records_found + 1 to your field with the proper formatting.

              I deleted my first response in here, but in it I mentioned that the OnSaveRecord field rule is triggered at the form level and is why your append which is a table method is not seeing that rule. I don't know if v9 has an honor field rules flag for the append operation. There are only a few rules that are honored when a flag is used - like auto increment and calc fields.
              Last edited by MoGrace; 06-29-2010, 11:07 AM.

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


              • #8
                Re: Append and Line Number

                Good morning Robin,

                Are you appending new records to a parent where existing records are already linked?
                Yes, I append the new records into Child table from 3rd table.


                • #9
                  Re: Append and Line Number

                  Good Morning!
                  In your thumbnail you show an embedded browse. Why not try this in your script that calls the append:

                  dim global vln as n = 0
                  vln = browse1:line_no.value

                  Then in the append

                  append.m_field1 = "line_no"
                  append.m_exp1 = "var->vln+1"

                  you will have to dim vln as global for the append operation to see it - and perhaps initialize at startup else it won't be available when you edit the operation. I am assuming line_no is numeric.

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