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

BeforeValidateNewRecords basic question

  • Filter
  • Time
  • Show
Clear All
new posts

    BeforeValidateNewRecords basic question

    I have a grid where the user fills in many rows at a time . The grid serves only for adding new records.
    Before saving, i would like to validate the rows, i.e there are some fields that must be filled if a row has been edited.
    How do i do that in the BeforeValidateNewRecords event? Also, what happens if there is only one "wrong" row and the rest are ok?


    Hi Jaime,

    Here is some from a grid. It doesn't do validation, but I'll an example of that. In the code below, you need to have the first two lines. They are already in the 'CanUpdateRecord' event, just make sure your code is after these two lines. This is where I do all validation that is not handled by the field rules.

    Result.Cancel = .f.
    Result.ErrorHTML = ""

    'update session variables if needed. If user is logged, then variables will be assigned
    dim session.userid as c
    dim session.userip as c
    if session.userid = "" then
    session.userid = api_getusername()
    end if
    if session.userip = "" then
    session.userip = api_getmachinename()
    end if

    'set fields values
    DataSubmitted.modified = now()
    DataSubmitted.modby = session.userid
    DataSubmitted.modip = session.userip

    'update the field fone1 to use this stored format. xxx-xxx-xxxx
    if DataSubmitted.fone1 <> "" then
    DataSubmitted.fone1 = left(remspecial(DataSubmitted.fone1),3)+"-" + substr(remspecial(DataSubmitted.fone1),4,3)+"-"+right(remspecial(DataSubmitted.fone1),4)
    end if​

    ''In the code above we simply assigned values to the fields modified, moody and modip. We record the date/time, userid and userip address for any changes made to a record. This code is also in the "CanInsertRecord' event and also has this code: (we also record the date/time, user and userip for each record when it added.)
    DataSubmitted.added = now()
    DataSubmitted.addby = session.userid
    DataSubmitted.addip = session.userip​

    'In the fone1 field we simply store the phone number is a certain format. The field rules already make sure that it is 10 digits long and contains no letters or spaces

    'if you wanted to validate the fone1 you could do something like this:

    if DataSubmitted.fone1 = "" then
    Result.Cancel = .f.
    Result.ErrorHTML = "Phone 1 cannot be blank"
    end if​

    Now having said that, you can also do the data validation in the Field Rules. When you have a field highlighted, then look at Display Settings, Validation XBasic. There is some sample code there to show you how. The advantage for this is that the error will appear next to the field. The event validation shows all errors at the top of the screen.
    You might also consider checking the 'Immediate validation' box. That will validate the field as soon as the user leaves the field.

    Hope that helps.
    Mike Reed
    Phoenix, AZ


      Many thanks Mike
      I do field validation of course. My issue is when the user just edits one field in one of the rows, does not fill "imperative" fields in that row, then submits all rows at once, so BeforeValidateNewRecords seems the right place. Will debug the event to see exactly what's exposed


        Makes you wonder if you can use the on blur event to return the user to the column not completed.
        Gregg is a great site to test and share sql code


          Thanks guys.
          The issue was fixed by entering my code into CanInsertRecord. I wonder what use is there for BeforeValidateNewRecords :-)