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

Empty Table vs Blank Field

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

    Empty Table vs Blank Field

    Hi all,

    I have MAJOR problems since the last patch. I've been reading about problems with deleting the last record in a table and I'm wondering if this is about that. I have many of the same scenerios in my database, and it seems they have all gone astray. I will describe one, and hopefuly get direction.

    I have a Table and Form "Donations" for entry of charitable contributions into the "Donations" table. I enter the donations, each with a unique identifier for each donation and a batch identifier for the group of donations being entered (details unimportant). At completion of entering the batch group, I have an operation (button-based) that Appends the entire batch to a second table(DoPosted), and also modifies with the Date(), a field 'poststate" in each of the records in the batch within the transaction (Donations) table. Worked great!

    I HAD a "catch" script called in the form Donation 'Exit' button, so that if the user hit this form 'EXIT" button without POSTING, it would 1) created the ~Variable: postcheck="", and 2) run the following script:

    (a5_get_records_in_query("donations",s_quote((Var->postcheck))+" = Poststatus")= 0)

    If .T., it would indicate the Post sequence had not processed and an error message would fire that "Posting had Not Occurred".

    All was well until the last patch. Now, if I enter to Donations form accidentally or need to exit witout entries, regardless of the entry condition= "No aditional selection criteria", if I immediately hit the form Exit Button, even if the first Action on that button is 'Cancel', there is established a record in that table that fulfills the above criterion and generates the 'catch message' and hinders my progress.

    What am I doing wrong?

    Mike W
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    #2
    oop, dyslexia

    Sorry the foolowing is the number of blanks=0

    a5_get_records_in_query("donations",s_quote((Var->postcheck))+" = Poststatus")= 0)

    If .T., it would indicate there were NO Blank Poststatus fields and the sequence Branches away from the error message firing of "Posting had Not Occurred".

    All-in-all, it seems to be about not being able to clear an entry process to a table.

    M
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment


      #3
      Mike,

      I can't make heads or tails out of your posts. Will need to see the app to look at the code in context I guess. My intuitiveness quotient must be running low this AM.

      One quick comment about "CANCEL" in an action script. Sometimes folks think it's intended to END an entire script. CANCEL and END are two different things.

      -- tom

      Comment


        #4
        Table refuses to be empty

        Tom,

        Sorry. I realize I was mixing accounting thoughts about "posting" which is different to a degree with database terms for posting. The database operations I am using are Append and then Delete all records in the transaction table, which youcan check out if desired in the attached database (please don't ask why this way,I was asked for it this way).

        I have narrowed it down to this:

        Opening a form to an empty table will generate a saved blank record when the form is closed using a Close Form action script when the Save Form On Exit box is checked. I have not found a way around this with tis box checked. The Cancel Changes command does not stop a blank record from developing in the table on Form Close.

        I don't remember this being this way before, but I'm probably wrong. Now that I am aware of this, I know I can't have my Close Form button action have a script that identifies a blank field as representing an incomplete operation.

        The attached database is an example. Open Form 2, Push Exit. Do it again. You end up having to delete the blank record that is generated on Save, to be able to Exit without the Alert, (based upon A5_get_records_in_query()=0 within the Exit script, being generated.

        Mike W
        Mike W
        __________________________
        "I rebel in at least small things to express to the world that I have not completely surrendered"

        Comment


          #5
          Possible solution ???

          Mike, I'm not 100% confident that this is a total fix. But maybe it will give you some ideas.

          Unzip the attachment to an empty folder.

          Form2 has been modified. There's a button that leads to an explanation.

          -- tom

          Comment


            #6
            in my experience, the easiest way to prevent accidental blank records, especially in browses or embedded browses is this:
            go to field rules for the table - goto events - record events - and cansaverecord

            Code:
            'since cansaverecord fires when you delete, you have to provide for it
            if a_deleting_record 'if you are deleting a record or a blank record, permit
                 end
            end if 
            t=table.current()
            if t.some field="" ' or some combination of fields are blank
                 cancel()
            end if
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment


              #7
              I'm golden

              Tom,

              Fabulous! Just what the doctor ordered. And it will fit into several places in my application, which is requiring many,many catches and checks as the user are part time volunteers.

              Than you so much for your tutelage.

              Mike


              Martin,

              Your script and approach would be great if the Cancel command would work in the situation. When the table contains no records, the Cancel command does not reverse the Enter Record action and will not convert the parentform to a View mode. But, I use for this elsewhere, so....thank you!

              Mike W
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment

              Working...
              X