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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Is there an equivalent to LISTNAV for disabling record navigation buttons in a list?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Is there an equivalent to LISTNAV for disabling record navigation buttons in a list?

    Does anybody know if there is a disable expression for record navigation buttons in a list, similar to 'LISTNAV_L1_first' disables the first button in a paginated list
    Tags: None
    #2
    Re: Is there an equivalent to LISTNAV for disabling record navigation buttons in a list?

    simply put, any button can be disabled by putting 1=2 in the client-side disable expression, if you're looking to create a more intricate process or set of rules to determine when it's disabled you might want to put another field hidden that is a yes or know value then create a switch case statement based on values in othe rfields or whatever your criteria might be. Thats just an idea, you might have to be a bit more specific in why and when you want it disabled - cheers~
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment

      #3
      Re: Is there an equivalent to LISTNAV for disabling record navigation buttons in a list?

      Hi Charles,

      Thanks for putting some ideas out there.

      My main use is where I am on a detail panel and the list is on another (hidden) panel. I have list record navigation buttons on the detail panel header. If I an entering/editing the first record in the list the First and Previous buttons should be disabled, if I am entering a new record then all navigation buttons should be disabled until it is saved and if I am editing the last record the Next and Last navigation buttons should be disabled.

      I do have some ideas how to achieve this with long winded algorithms but wondered if anyone knew of the LISTNAV equivalent for record navigation. Unfortunately the LISTNAV help topic is under construction and this may have been a starting point.

      Comment

        #4
        Re: Is there an equivalent to LISTNAV for disabling record navigation buttons in a list?

        My first thought is why have ANY buttons for navigation showing when editing, or entering a new record? Perhaps this is just more of a flow issue in what controls are actually there in the first place...Perhaps you should use the list to show the detail view when navigation is showing and the detail view only when editing or entering new.
        I think that is the way it was intended in the first place, and perhaps why it's becoming difficult to get what you want.
        I certainly respect your vision of what you want, but I think if you would consider a different layout you might get better results.
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment

          #5
          Re: Is there an equivalent to LISTNAV for disabling record navigation buttons in a list?

          Also, just as a side note. Sometimes I create a few dummy fields that have a calculated value of the same actual detail view field. This allows me to display the value without fear of edits or write conflicts because it is a totally unbound field. You could do the same to display just the values of the detail view you want with record navigation - then if a user decides to actually edit you coudl use a button to bring them to the real detail view controls with a save button. Just a thought!
          NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

          Comment

            #6
            Re: Is there an equivalent to LISTNAV for disabling record navigation buttons in a list?

            Hi Charles,

            Thanks again for your thoughts.

            The main issue is the detail view panel needs to be full screen because of the number of fields involved and a child list with it's detail view as well(this is only visible if the parent key field is greater than 0), therefore the list is not visible.
            Data entry for the main list, in it's detail view can be very quick because of a dropdown control which appends part/full commonly used sentences to the list. The use of navigation buttons avoids the need to go back and forth between the list panel and its detail view panel to check previously entered data. This is something that has evolved since I first discovered lists back in version 11 and is in use daily. Just seems frustrating when you hit the next button only for nothing to happen and then realise you should have hit the new record button. If the next button was disabled, as in a paginated list, it wouldn't happen.

            Comment

            Previous template Next
            Working...
            X