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

How to avoid blank records.

  • Filter
  • Time
  • Show
Clear All
new posts

  • How to avoid blank records.

    If you have a form to fill customer information. you are in enter mode, and you decide to cancel entering data or have a BUTTON ON THE BOTTOM to close the form or press "X", and when you press the close button it make a blank record.How could you avoid from creating a blank record..

  • #2
    Re: How to avoid blank records.

    I have run into this problem as well. My solution was to create an operation that I run periodically to delete blank records. In my people table, I identified blank records as records with no first & last name or with no unit ID. A5 generated the following code:

    a_tbl ="tblpeople")
    ON ERROR GOTO ERROR22092008225239691
    GOTO CONTINUE22092008225239691
    ui_msg_box("Error","Error running Mark/Un-mark/Delete Operation"+crlf()+error_text_get())
    a_tbl.close()'If the Operation is run from within a Form or Browse, then refresh the window
    if is_object(topparent.this) then
    	if topparent.Class() = "form" .or. topparent.class() = "browse" then
    	end if
    end if
    I run this operation in the On Push event of the button that closes the form that potentially could add the blank record. This seems a little crude, but it has solved the problem.

    -- Dick James


    • #3
      Re: How to avoid blank records.

      Mike, Dick,
      Another popular way is in field rules using something along the lines of the following.
      Just copied this from a text file I have had in my help file for a long time--I have found Many, Many examples of similar on the messageboard.
      go to the table, field rules, record events, cansaverecord and add this: take one or two fields that you would require
      e.g. custname, invoicenumber
      if t.custname="" .or. t.invoicenumber="" 'nothing
      cancel() 'will silently cancel the entry
      end if
      EDIT--Mike, welcome to Alpha BTW! You should be able to find most answers either in the help file or by searching on the messageboard. But if you cannot find what you need then for sure do as you just did and ask the good people here.
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau


      • #4
        Re: How to avoid blank records.

        Thanks MikeC and DickJames for your help, sorry it took me so long to tahnk you


        • #5
          Re: How to avoid blank records.

          Originally posted by Mikepatel View Post
          Thanks MikeC and DickJames for your help, sorry it took me so long to thank you


          • #6
            Re: How to avoid blank records.

            Wouldn't it be easier to just set a field rule on any field to 'always required'?


            • #7
              Re: How to avoid blank records.

              Have you ever tried this? I personally think it is very restrictive...can actually be very annoying in fact when you get to the field and cannot get out without placing a value in the field prior--even though you may just want to forget about entering in the record and just cancel.....

              Along with that, the script I gave simply is an easy way to prevent a record from being saved that does not have all the field values necessary to constitute a "saveable" record. Making one of the fields required can actually result in more coding if you want to just cancel as then you would have to add code to the cancel script to eliminate the value in the required field that was necessary to even get out of the field.....

              There are uses for having a required field but I wouldn't like to use it for blank record prevention

              I think I made my point or at least my personal reasons for not using field rules to have a required field. :) .Much depends upon what is needed is all.
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau