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

Plunging into xbasic, finally!

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

    Plunging into xbasic, finally!

    I'm working on a student quiz application.

    I have 3 fields on a grid:

    1. The correct answer (it will be hidden).
    2. The student's answer.
    3. The status of the answer.

    The grid will show only 1 row at a time.

    If the student's answer is correct, I want the status to show "correct". If it's incorrect, I want the status to say, "not quite."

    I'm thinking this is an "after validate" event. I'd really appreciate it if someone would point me in the right direction. I do not have to store the answer, only indicate whether it's status is "correct" or "not quite."

    Many thanks!

    --Rob

    #2
    Re: Plunging into xbasic, finally!

    Rob,

    There are so many ways to approach this.

    I would probably use the Validate event, because by putting your xbasic there, you can more easily get the appropriate messages to display on the SAME page.
    Gary S. Traub, Ph.D.

    Comment


      #3
      Re: Plunging into xbasic, finally!

      Gary,

      I appreciate your help. May I impose upon you for the direction in which I should go regarding the code? Is this an "if" event?

      Thank you.

      Rob

      Comment


        #4
        Re: Plunging into xbasic, finally!

        Rob,

        More than happy to help in any way I can.

        Actually, this is a grid, not a dialog, so no Validate event - You can use the CanUpdateRecord event, with code something like:

        if DataSubmitted.thefield="the wrong answer" then
        Result.Cancel = .t.
        Result.ErrorHTML = "Wrong answer - try again!"
        end if
        Gary S. Traub, Ph.D.

        Comment


          #5
          Re: Plunging into xbasic, finally!

          Rob,

          Something I found of interest in doing a test with TEXT answers was using SoundEX

          eg
          vQuestion = "Who made this Test ?"
          vAnswer = "RobPoley"

          if (Soundex(RobPolley) = Soundex(vAnswer) Then
          ---
          ---
          ---

          This provides some leeway for users

          Comment


            #6
            Re: Plunging into xbasic, finally!

            Colin,

            That may solve another issue; thank you!

            --Rob

            Comment


              #7
              Re: Plunging into xbasic, finally!

              I'm getting the validation to work; I appreciate your help.

              Is it possible to alter the format that the validation box assumes?

              For Example, the heading is "Validation Errors"

              I'd rather not have any heading.

              It also indicates the row number, which I'd rather not have.

              Finally, I'd like to change the font size.

              Is it possible to do any of this?

              (I have been able to move the small section of the grid component that contains the validation error message.)

              Thank you!

              Comment


                #8
                Re: Plunging into xbasic, finally!

                On my test system, I now have a "Can update record" event working to show that an answer is incorrect.

                I have not been able to show that it's correct. I suppose that "no response" could equal a correct answer, but I was hoping to have responses for both incorrect and correct answers.

                For some reason, I think that Result.ErrorHTM will display only if result.cancel=.t.

                I'd like to display a message if result.cancel=.f.

                Is this possible?

                Thank you.

                --Rob

                Comment


                  #9
                  Re: Plunging into xbasic, finally!

                  Rob,

                  To have more control, like what you want to do with the error message, you should use a dialog instead of a grid.

                  However, assuming you will stick with a grid, the result.cancel=.t. is not referring to whether the answer was right or wrong. It refers to whether to trigger an error message or not. If it is .t., then the 'cancel' tells a5 not to commit the record, and to display an 'error' message. in your case, you want that to be .t. in either case, something like:

                  if answer is correct
                  Result.Cancel = .t.
                  Result.ErrorHTML = "Correct answer - good job!"
                  else
                  Result.Cancel = .t.
                  Result.ErrorHTML = "Incorrect answer - try again!"
                  end if
                  Gary S. Traub, Ph.D.

                  Comment


                    #10
                    Re: Plunging into xbasic, finally!

                    Gary,

                    That was my hunch, but I must have written the code incorrectly. I'll try again.

                    Thanks, also, for the tip on dialogs. I have used them only to create a "print" button. I guess I'll take the plunge there, too.

                    Thank you for your help!

                    --Rob

                    Comment

                    Working...
                    X