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

Cancelling new record entry on embedded browse

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Re: Cancelling new record entry on embedded browse

    Don't know whether this is covered or not Earnie, but I've added a "Save Record" when moving away from Browses and more importantly, Memo fields. Its easy to lose the data if you don't.

    Don't understand why the field rules requiring data doesn't work though.

    Thanks for the info Tom. I bet a few don't know about the field "padding".
    See our Hybrid Option here;


    • #17
      Re: Cancelling new record entry on embedded browse

      I think I had topparent.commit() on the button that moved to next form. I've moved on to adding records to a browse with a form. I thought once you moved off the browse record, it was automatically saved/committed, therefore making my first sentence un-needed. It's still a mystery to me.


      • #18
        Re: Cancelling new record entry on embedded browse

        Have you got it sorted Ernie? I'm back home and developing a software robotics test management suite as fast as my fingers can press the keys!
        Give me a shout if you are still struggling.
        See our Hybrid Option here;


        • #19
          Re: Cancelling new record entry on embedded browse

          Sorry Ted. Just now found your reply. The way I sorted it was to just upgrade the app to ver. 10.5. I feel the browse issues with ver. 9 are just too non-reliable to deal with at this time.
          Now I'm having an issue with the 10.5 browse, but is just too sporadic to get anyone to test.


          • #20
            Re: Cancelling new record entry on embedded browse

            Well I'm taking my laptop to work next week, and have V9 and v10 loaded, so gimme a shout if you want to.
            See our Hybrid Option here;


            • #21
              Re: Cancelling new record entry on embedded browse

              I have a form based on a set. The top table is a dummy table with a date. There is a one to many browse on the form. There are many fields also on the form from various one to one linked tables as well. If I enter any data in one of the fields from a child record, a record is created in that child table. I tried, as a test, in the child table to use both of the two examples above in the cansaverecord event in the field rules.

              if t.resnum<=0 then
              end if

              does not stop a record entry if I use a pull down or text box. If I try to edit a field it still does not stop it as I jump from field to field. If I try to close the form, then I get an error:
              Property not found
              t.resnum subelement not found.

              If I try:
              dim t as p
              t = table.current()
              if isblank(t.resnum) then
              end if

              Nothing seems affected in the form based on the set. If I open up just the table itself and attempt to change a record with a blank resnum field I get:

              it tells be that isblank (t.resnum) that the argument is the incorrect data type.

              I am a bit frustrated here, if anyone has and idea, that would be great.


              • #22
                Re: Cancelling new record entry on embedded browse

                The Help format suggests that the syntax is
                if isblank("t.resnum") then
                Is appropriate.
                You are testing the content of the Field, not the value.
                See our Hybrid Option here;


                • #23
                  Re: Cancelling new record entry on embedded browse


                  Is the "resnum" field the "link" field in your child table?

                  If so, remember that your set based form will autofill that field when you begin data entry into any field of the linked table. So, it won't ever be blank.

                  -- tom


                  • #24
                    Re: Cancelling new record entry on embedded browse

                    True, the resnum is the link field, however, it does not fill in nor is any other record created except within the table in which the data is entered. After a record is created if I view the individual table, the resnum field is indeed blank. If I try to manipulate the data in that table, not in the set form, I can change anything and nothing happens. If I try to create a record in that table, it will not let me leave the record without canceling it. I cannot save it, but I cannot navigate away from the record either, it is quite strange.


                    • #25
                      Re: Cancelling new record entry on embedded browse

                      John, it sounds like your script is sending Alpha to lala land. It's time to post a sample of your database here, with instructions for us to follow to see the behavior you're describing. I have to tell you in advance that your form design is the likely culprit. Data entry in Alpha Five is done in tables, not in sets. It's very likely that if you use the default form for your set you won't have the same issues.