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

validating information

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

    validating information

    After a user presses a button and asked for the Serial_number to find, it will search for that serial number. If they enter some off the wall number like 999999, it will bring up the last serial number, which to date is 133082. Can I make this not happen. What I'm saying is if they enter an off the wall number, that is not in the current database, can I display an error and force them to re-enter? They will be scanning the serial number, so that should eliminate the mis-entry, but I'd like to be safe. Any thoughts?

    #2
    RE: validating information

    Donnie,

    Why not use the "Key_exist" function?? If the user enters a serial number, compare what they entered with existing numbers (provided the serial number is an index). If the key doesn't exist, then send a message box stating so and force tem to re-input the number.

    Tom Henkel

    Comment


      #3
      RE: validating information

      I assume you are using a button to "goto" the desired record.

      You should be able to code xbasic to store the current record number to a variable, store the desired serial number to a variable, perform the search, check the desired serial number against the serial number of the fetched record, display a message if they don't == exactly match, and return to the original record number.

      That's the process I think will work. Let us know if you need help with the coding.
      There can be only one.

      Comment


        #4
        RE: validating information

        Stan,

        If it was in COBOL or C, I could do it, but I'm relatively new to xbasic. Any help on the coding would be great. Thanks.

        Comment


          #5
          RE: validating information

          Hi Donnie - Here is a script attached to a button on a form to find our serial numbers. You will have to substitute your .dbf and index names were needed.

          dim shared tbl as p
          dim shared part as c
          dim vserial as n
          dim query.description as c
          dim query.options as c
          dim query.order as c

          tbl=table.current()
          tbl.index_primary_put("serial")
          part=ui_get_text("Find A Serial Number","What is the number?")
          vserial=val(alltrim(part))
          if part="" then
          tbl.index_primary_put("serial")
          tbl.fetch_first()
          parent.resynch()
          end

          else
          query.description="Snumber"
          query.order="invert(date)"
          query.options=""
          query.filter="vserial=serialno"
          indx=tbl.query_create()
          rec_count=indx.records_get()
          Recs=rec_count
          if rec_count=0 then
          ui_msg_box("","Serial Number "+upper(ltrim(part))+" not found. Displaying all records.",ui_attention_symbol)
          tbl.index_primary_put("serialno")
          parent.resynch()
          end

          else

          tbl.index_primary_put("serial")
          parent.resynch()
          end if
          end if
          end

          Comment


            #6
            RE: validating information

            Donnie,

            Are you doing the scanning with a table lookup field rule?

            -- tom

            Comment


              #7
              RE: validating information

              Not using a lookup, just a comparison.

              Comment


                #8
                RE: validating information

                Ok. However, if you haven't considered using a table lookup it might help. It's an easy way to assure that the user always enters a value which exists in the lookup table. They just pick the one they want right off the list.

                -- tom

                Comment


                  #9
                  RE: validating information

                  Thanks. We'll give that a shot.

                  Comment


                    #10
                    RE: validating information

                    Donnie,
                    I do the same thing. Try this code in the onDepart event of the field:

                    dim shared vSn as c
                    dim pTbl as p
                    dim pIndx as p
                    dim recno as n
                    if alltrim(vSn)=""
                    end
                    end if
                    pTbl=table.current()
                    pIndx=pTbl.index_primary_put("serialno")
                    recno=pTbl.fetch_find(vSn)
                    if recno
                    Pat Bremkamp
                    MindKicks Consulting

                    Comment


                      #11
                      RE: validating information

                      Attached is a script we use to force our workers to find clients by specific indexes. We require the workers to input specific data based on thier search selection. We verify that the input data exists, then, if OK, go to the records. It is fairly intricate, and I don't expect that you will use the entire thing, but I hope it helps you to get your desired results.

                      Tom Henkel

                      Comment

                      Working...
                      X