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

Confirm Password Change in a Grid

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

    Confirm Password Change in a Grid

    Hello,

    I have an application in which I want to allow users to be able to change their passwords. As with many Web apps, I want to ask the user for the password twice, to make sure they type it in correctly.

    If the passwords they enter don't match, I don't want to update the password in the table.

    I know I can do this using a dialog and some Xbasic (and it wouldn't be that tough), but does anyone know of a way to do this in a grid?

    Thanks!

    dm

    #2
    RE: Confirm Password Change in a Grid






    p { font-family: Tahoma; font-size: 8pt; margin-top:0; margin-bottom:3pt }
    h1 { font-family: Tahoma; font-size: 12pt; color: #0000FF }
    h2 { font-family: Tahoma; font-size: 10pt; color: #0000FF; margin-bottom:0pt }
    h3 { font-family: Tahoma; font-size: 8pt; color: #0000FF; margin-bottom:0pt }
    .xbasic { font-family: Courier New; font-size: 8pt; color: #0000FF; margin-left: 20pt }
    li { font-family: Tahoma; font-size: 8pt; margin-top:0; margin-bottom:3pt }
    td { font-family: Tahoma; font-size: 8pt; margin-top:0; margin-bottom:3pt }
    .sampleCode { font-family: Courier New; font-size: 8pt; color: black; margin-left: 20pt }
    -->


    This will be much easier to do in v2 of the grid component because it will support events.However, you can still do it with the current grid using some clever programming.If you edit the page that contains the grid component, you will see, in the head section of the page, the code that loads and runs the grid component.You need to insert some code here BEFORE the component is loaded and run.Say, for example, that your component name is 'grid1' and that the password fields are called 'pwd1' and 'pwd2'.I will assume that you have set your grid to only show 1 row of data and that the grid is Update only (i.e. you have turned off the ability to enter new records). I will also assume that if the user does not enter the correct values, you want to redirect to another page called 'errorpage.a5w'.If you look at the HTML that is generated by the grid, you will notice several things.1. When the user clicks the submit button to save changes, a variable is submitted to the server called'grid1_Button_Submit' and it has a value of "Submit" 2. The variables that are submitted back for the 'pwd1' and 'pwd2' fields are called 'v.R1.pwd1' and 'v.R1.pwd2'Knowing this, you could write this Xbasic:(The Xbasic tests if the grid1_button_submit variable exists - it will if the user has clicked the submit button. it then checks to see if the password fields match. if not, it redirects the browse to the 'errorpage.a5w' page) if eval_valid("grid1_Button_Submit") then if v.r1.pwd1 "" v.r1.pwd2 then response.redirect("errorpage.a5w") end end if end if Important: The 'grid name' (grid1 in this example), is NOT necessarily the name of the component as it appears in the web control panel. It is the component name property assigned in the page. e.g. you will see code like this on the page:with tmpl componentname = "grid1"end with The name shown above is the component name you must use when constructing the name of the variable that is submitted when the user clicks the Submit button.Note. If you did not want to redirect to an error page, but you wanted to prevent the changed being committed to the database, you could simply do this: if eval_valid("grid1_Button_Submit") then if v.r1.pwd1 "" v.r1.pwd2 then delete request.variables.grid1_button_submit end if end if Advanced User Note: The reason that we delete 'request.variables.grid1_button_submit' and not just 'grid1_button_submit' is that the code that runs the Grid sees the variables that were submitted by getting a pointer to 'request.variables'. Deleting the variable 'grid1_Button_Submit' does not delete this variable in the 'request.variables' namespace.

    Comment


      #3
      RE: Confirm Password Change in a Grid

      Thanks Selwyn.

      I'll give this a try today. I love using the grids, because the save me a ton of time (and look nice). Look forward to V2!

      dm

      Comment

      Working...
      X