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

SetFocus to NewRecord OR Create Button to replace "Enter new Record" on Grid

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

    SetFocus to NewRecord OR Create Button to replace "Enter new Record" on Grid

    I have seen something about this in the past, but have been searching for hours and not found what I need.

    Problem:
    when multiple users are entering records into an "editable" grid, the records are "jumping'. ie they enter record, and when they "save" the record appears to be lost to them (it's really just on the LAST page).

    I have tried setting the fields in the Grid Update to only add new record on last page. However, that only puts it at the bottom of the CURRENT page. I cannot seem to force the new record to FIRST move to Last page, THEN add new record.

    I have tried doing an ajaxcallback in CanNewRowsShow with variations of the following: (I have also tried other Client Side, as well as some ServerSide, all to no avail)

    REturn this javascript from callback: (which the 'alert' works, but doesn't seem to do anything prior to 'alert')GoToLastPage= "var rowNum = GRID1_GridObj._rowsInGrid; {grid.Object}.setSelectedRow(rowNum);alert(rowNum);"

    OR embedding this directly in the callback and only returning 'alert' [again, alert then works but does not go to last page]
    <<%js%
    {grid.Object}.pageNavigate('last');
    %js%

    AND I have also tried just returning :
    gotolastpage="{grid.Object}.pageNavigate('last');"

    AND I have tried just putting {grid.Object}.pageNavigate('last'); directly in CanNewRowsShow, in which case
    1)FIRST the new record row is added to users current page
    2) THEN the pointer is moved to last page.

    This just seems like an everyday thing that people would want to do (go to last page before doing new enters) and should not be this difficult.
    It's probably very simple, but I just can't make it work.

    #2
    Re: SetFocus to NewRecord OR Create Button to replace &quot;Enter new Record&quot; on Grid

    A few things that come to mind on this one.

    1 Simply make the newest rows first that way they can see the entry right away.

    2 Create a simple grid that contains only the last entry filtered by the user and put that grid above or below the grid so that when they submit it shows them that they can see the last entry that they made.

    3 Create a couple of variables that you could use in a msg and put the message above the grid.. something like last entry by you was e.rv.session.lastinv and whatever else may be relevant.

    I have used all 3 before each have their benefits.
    Chad Brown

    Comment


      #3
      Re: SetFocus to NewRecord OR Create Button to replace &quot;Enter new Record&quot; on Grid

      Originally posted by chadbrown View Post
      A few things that come to mind on this one.

      1 Simply make the newest rows first that way they can see the entry right away.

      I have used all 3 before each have their benefits.
      Thank you Chad for your suggestions, all very good. I can probably make do with the first one.

      I am using Row Expander Grids with the main grid. After a user Inserts New Record, they may or may not need to enter a New Record in the RowExpander Grid, which is why I really need the focus to stay on the Newly Inserted Record after Submit.

      This is a Feature that I really thought A5 would include in their V11, just seems like such a common need.

      People should be able to, with a few clicks under Grid Update Settings, choose how they want the Insert Properties (NewRecordHyperlink) to work:
      1) should be able to force position to last Record in Grid prior to insert
      2) should be able to say "stay on Newly Inserted Record" after Submit
      3) should also be able to choose if we want the NewRecordInsert Hyperlink to be a Hyperlink or a button, without any additional programming.
      4) should make the NewRecordInsert Hyperlink "editable" under Grid Update Properties, just like other buttons or ActionButtons are editable.

      Maybe this is already included, and I just don't know where to look. But this should not cause people brain injury.

      Comment

      Working...
      X