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

Embedded Browse - go to Latest Record

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

  • Embedded Browse - go to Latest Record

    Members,

    I am an amateur user, and can normally work out a way (mostly trial and error!) on how to solve a problem. I've spend a good deal of time on this, so I thought best to ask if there is a solution that I just can't seem to find.

    I have a set and within this is a one-to-many embedded browse which holds transactions for the particular person. Some records now have many dozens of transactions, and when moving to any particular record, the embedded browse always shows the earliest transaction. It then means scrolling down, as it is the latest ones that I normally want to look at. I've added a couple or screen shots to show what I mean.

    Any suggestions please?
    Attached Files

  • #2
    Re: Embedded Browse - go to Latest Record

    See the AlphaSports invoice form. There's a button on the form (Bottom) with the code

    browse1.fetch_last()
    browse1.activate()
    There can be only one.

    Comment


    • #3
      Re: Embedded Browse - go to Latest Record

      Thanks, Stan.

      I've added the buttons I need and it works fine - apart from me needing to change the AlphaSports coding to, for example, from browse1.fetch_last() to Control_browse1.fetch_last().

      I was thinking the wrong question, in that I was looking for the active record in the embedded browse to be the latest by default, and effecting this was my difficulty taking account of my limited knowledge/expertise in coding (though A5 has enabled me to do more than I expected over the years). Using a single mouse click is not a hardship at all compared with having to scroll though numerous lines in the browse.
      Last edited by Esio Trot; 12-17-2017, 08:45 AM. Reason: Typo

      Comment


      • #4
        Re: Embedded Browse - go to Latest Record

        David

        Now you can use that code in another event that will cause the repositioning of the record pointer without a click of a button.

        You could try the onfetch event of the form - it works (thanks for the reminder Stan..) ;) ...
        Last edited by Al Buchholz; 12-17-2017, 04:27 PM.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


        • #5
          Re: Embedded Browse - go to Latest Record

          You can go into the Filter/Order tab of the Form Properties, select the table which the embedded browse is based on, and select the order that you want to display the records in the browse - maybe INVERT(Trx_date)?

          Comment


          • #6
            Re: Embedded Browse - go to Latest Record

            Originally posted by LDK View Post
            You can go into the Filter/Order tab of the Form Properties, select the table which the embedded browse is based on, and select the order that you want to display the records in the browse - maybe INVERT(Trx_date)?
            Good idea, but that serves a different purpose.
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


            • #7
              Re: Embedded Browse - go to Latest Record

              Or set the order on the child table to the required column and tick/untick descending as needed.

              Comment


              • #8
                Re: Embedded Browse - go to Latest Record

                The display order of the child records seems to be on the Transaction Description column. Which is probably why 'Article 23 Liability' appears first in the list and the date fields are not sorted. Assuming the records are being entered in the Date field order, then record order would give you a proper display. However, if they are being entered randomly, then you might want to set the order for the child records in the form's properties to something like 'cdate(date)+transaction_description'. Which of course is up to you, but the current display seems odd to me. Then fetching the last record in the browse will give you the most recent payment entry by date - which btw, would put 'Article 23 Liability' last in the list.
                Last edited by MoGrace; 12-21-2017, 12:54 PM.
                Robin

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

                Comment

                Working...
                X