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

Restricting New Record on Embedded Browse

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

    Restricting New Record on Embedded Browse

    I'm trying to restrict (prevent) the new record entry line from appearing at the end of an embedded browse. Checking and unchecking the 'New Record' restriction box on the browse itself properties prevents it in the browse proper, but still allows it in the embedded browse. Checking & unchecking 'New Record' on the embedded browse properties doesn't seem to have any effect.

    Can anyone confirm this (or tell me what I'm doing wrong)?

    Bob Arbuthnot

    #2
    Re: Restricting New Record on Embedded Browse

    Would be happy to. Please post a working sample, with instructions for us to follow to test it on our systems. -- tom

    Comment


      #3
      Re: Restricting New Record on Embedded Browse

      works Ok here.

      Comment


        #4
        Re: Restricting New Record on Embedded Browse

        Thanks Gabriel and Tom,

        I got to the bottom of it. If the form is set to modeless or your default is modeless, then the Restriction settings on the embedded browse don't "stick" when you save the form. Maybe that follows logic, but it seems like if the form is modeless, then the checkboxes on the embedded browse -> Properties -> Restrictions should be grayed out or at least have some on-screen documentation to the effect that these check boxes are only active if the form is modal.

        Is this a bug? A quick review of the chm I don't think makes any mention of form data entry mode. I'll submit a bug report if anyone else out there thinks it is...

        Bob Arbuthnot

        Comment


          #5
          Re: Restricting New Record on Embedded Browse

          Bob:
          Good detective work and yes I think it's a bug. Modal or Modless should not affect restrictions.

          Comment


            #6
            Re: Restricting New Record on Embedded Browse

            Bob:
            I am confused by what you are saying. With an embedded browse, if you don't want to generate a new record by advancing to the next row, the only option, I believe, is to go to data entry and click on modal. If you want to totally restrict any new addition, you go inside the browse properties and click on the new record check box that restricts anyone from adding a new record. So, if you are in modeless, you can prevent any addition of a new record by clicking on the restriction checkbox for new record. In modal, you can overridden the ability to not add a new record (that row doesn't appear), by using action scripting to add new record button (but you must not check new record restriction box). The newly created button then overides the modal situation of not having the new record row available. There is no bug, as far as I can tell.

            Pete
            "Ollie, remember how dumb I used to be? Well, I'm much better now."

            Pete

            Comment


              #7
              Re: Restricting New Record on Embedded Browse

              Pete:
              So, if you are in modeless, you can prevent any addition of a new record by clicking on the restriction checkbox for new record
              Yes, but that's is not happening with the embedded browse. If you are in Modless data entery and check the restriction for new record in the browse, it does not stop you from adding a new record and that's the bug. Evidentlly, the parentform's settings overrides the mebedded browse's setting.

              Comment


                #8
                Re: Restricting New Record on Embedded Browse

                Bob, I agree with Gabriel it sounds like something that should be reported. I hope you'll take a few minutes and send along a working example for them to see. This avoids communication issues, and increases the likelihood that an early fix will be forthcoming. -- tom

                Comment


                  #9
                  Re: Restricting New Record on Embedded Browse

                  Bob and Tom:
                  I find that there are two areas on the form where you can restrict the new record. For the embedded browse, I clicked on the embedded browse, then go to properties on the restricted side and checked off restricting new record. If I click on a blank area of the form and go to properties there is also a restricted area for new records. Checking that one off stops the parent record from advancing to a new record. This is using the system default button or the modeless button. Both work for me.


                  OK, I just read G's comments and do not find that happening. I am in modeless, only check off the restrictions in the browse and can't add in the browse. I will play with it some more. I did originally see what G and Tom describe. I tried it again, with the same results. The parent can add a record and the child has no adding ability. I am using the latest build 1367, 3067.
                  Last edited by trackmanpete; 03-18-2007, 07:52 AM.
                  "Ollie, remember how dumb I used to be? Well, I'm much better now."

                  Pete

                  Comment


                    #10
                    Re: Restricting New Record on Embedded Browse

                    Pete, Tom, Gabriel,

                    Sorry to be slow getting back to this, had to watch some basketball the last 24 hours.

                    I was wrong in my earlier 'solution.' Setting the form to modal does solve my problem of preventing the new record line from appearing at the end of an embedded browse. But, for the life of me, I can't make the check marks "stick" in the form->embedded browse->browse properties->restrictions. I can check whatever I want, save, close the form, reopen in design mode, go back in and the check marks are gone. I've tried it with the form both modal and modeless.

                    So, even though my original problem was solved by changing the form to modal (which is the way I wanted it anyway), I guess I'm not using or don't know how to use the 'Restrictions' correctly.

                    Anyone care to enlighten me?

                    Sample DB attached.

                    Bob Arbuthnot

                    Comment


                      #11
                      Re: Restricting New Record on Embedded Browse

                      Bob:
                      Now, G and Tom are the experts on this forum, as you know, but I thought I would take a shot. What I found is that you are correct when you download an existing embedded browse. I tried making canceling add record and could also not get it to work. However, when I built an embedded browse on the form, it works fine. I prefer building the embedded browse, so I can see the rows and make adjustments to column width and row height. Placing an existing embedded browse only shows a box and you need to go to properties to make the necessary changes, I think. So, I made the changes to your sample and see what you think. Kansas looked good!
                      "Ollie, remember how dumb I used to be? Well, I'm much better now."

                      Pete

                      Comment


                        #12
                        Re: Restricting New Record on Embedded Browse

                        Hi,

                        I believe a bug HAS been discovered here. On the example Pete posted, it works as expected... you have a modeless form that you can add a new record to simply by getting to the last record in the table, and pressing Page Down or pressing the Add New Record button. However, due to the "Add New Record" restriction in the EMBEDDED browse, if you are in the browse, pressing Page Down will NOT allow you to add a new record. Only pressing the Add New Record button will work.

                        Now, if you put a NAMED browse onto the form as an embedded browse, and give that NAMED browse the same restriction (can't add new records), that restriction seems to be IGNORED.

                        Am I understanding this correctly? If so, I believe Gaberiel mentioned this earlier; I think there is a bug...

                        Comment


                          #13
                          Re: Restricting New Record on Embedded Browse

                          There is an alternate way to prevent 'new record' from ever appearing for any form or browse.....

                          In the base table make a Character field with size 1..
                          You can call it what ever you want... I call it 'nonewrec'.

                          When you create the form, place the 'nonewrec' field on the form somewhere; hidden (if you feel that necessary). Make the field the last tabbed field on the form. Go to the field event 'OnArrive' and enter the code to activate the first tab field on the form. Action Scripting can accomplish this -- or XBasic; whichever you prefer.

                          Whenever you tab onto this field, the tab will go to the first field on the form. This means you will have to manually activate the 'new record' function. I personally set all my forms to 'no edit' and manually start each new record or record change. Also, I hide the field in the top banner by having no border on the field, no label, and making the field the same color as the banner. The field will show up when in design mode but the user will never know that it exists..... Learned this some time ago right here on the forum.

                          D

                          Comment


                            #14
                            Re: Restricting New Record on Embedded Browse

                            Shawn:
                            I think you are right. The check box to restrict enter record does not seem to hold when using a saved or "named" browse. I was able to restrict entry by have the form set to modal. That is different from using a created browse on the form where the add record restriction does hold.

                            So, it seems that this is a bug with a work around, but still a bug.

                            Pete
                            "Ollie, remember how dumb I used to be? Well, I'm much better now."

                            Pete

                            Comment


                              #15
                              Re: Restricting New Record on Embedded Browse

                              Hi Pete,

                              Thanks for the example, and for setting me straight. It does appear we all agree that the 'Restrictions' check boxes are ignored in the properties of a named browse object that is placed on a form.

                              I'll try and get a bug report sent in, although this is fairly minor.

                              Re: Hoops. Amazing, isn't it, how easy the game is when the ball is going in the hole?

                              Bob

                              Comment

                              Working...
                              X