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

Custom Browse Not skipping Field as set in Rules ( later on)

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

    Custom Browse Not skipping Field as set in Rules ( later on)

    Greetings,
    I'm a new user and working my way through the basics (what a long learning curve ahead, but enjoying it). I created a table with an auto-incrementing key field, and had set it to user required. I then created a custom browse on that table. I later realized that I need to set skip to true (and I guess set required field off) to have A5 create the next value and skip to the next field automatically when entering new records. This works as expected in the default browse but my original custom browse does not reflect this field rule change, the cursor sits in the id field. I created a new test custom browse on the table, and it works as expected.

    It seems that a custom browse is "static" and is not aware of subsequent field rule changes, is that a correct assumption? So I need to be sure to have my field rules nailed down, or I have to go back and recreate a browse ... am I missing something?

    Thanks,
    Mark

    #2
    Re: Custom Browse Not skipping Field as set in Rules ( later on)

    I've just tried to replicate what you have described Mark, and cannot.
    I believe that when a Browse or Form is reloaded, the Field Rules are honoured. This is what happens in my TestBed.
    Suggest you try running a Compact after a few changes.
    Did you have the Browse open when you made the changes? You will/might have got an error message but can still apply Rules Changes.
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    Comment


      #3
      Re: Custom Browse Not skipping Field as set in Rules ( later on)

      What you can try in the browse is remove the default TAB in the column properties - that will skip the field too. Just be aware that if it is the first column in the browse and you scroll to the last field past the browse width, you will not be able to get the first column to display using the HOME key, but can with the horizontal scrollbar.
      Robin

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

      Comment


        #4
        Re: Custom Browse Not skipping Field as set in Rules ( later on)

        Ted, Robbin,
        Thanks for your input. I still can't seem to fix my browses, although new ones obey the rule. The tab setting still leaves the cursor in the ID field, but I know how it works now. I included 3 pngs of the data entry field rule for the env_id field, the default browse (although you can't see the cursor in the 2nd field, and the 3rd shows my custom browse where the ID field doesn't get skipped, it just remains highlighted, strange ... -Mark
        S1.PNGs2.pngs3.png

        Comment


          #5
          Re: Custom Browse Not skipping Field as set in Rules ( later on)

          Skip needs to evaluate against a Value.
          Suggest [Envid>""] rather than [.t.]
          See testbwse attached.
          Attached Files
          Last edited by Ted Giles; 10-17-2011, 03:45 AM.
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          Apologies to anyone I haven't managed to upset yet.
          You are held in a queue and I will get to you soon.

          Comment


            #6
            Re: Custom Browse Not skipping Field as set in Rules ( later on)

            Skip needs to evaluate against a Value.
            The use of .T. as the skip expression is common. It just means that the field is always skipped.
            There can be only one.

            Comment


              #7
              Re: Custom Browse Not skipping Field as set in Rules ( later on)

              Of course you are correct Stan, but I don't believe that I have ever used it like that.
              When skipping, I have always put a reason for the skip.

              Mark, what happens if you put another type of expression into the Skip expression field?
              Or have you fixed it?
              See our Hybrid Option here;
              https://hybridapps.example-software.com/


              Apologies to anyone I haven't managed to upset yet.
              You are held in a queue and I will get to you soon.

              Comment


                #8
                Re: Custom Browse Not skipping Field as set in Rules ( later on)

                I pretty much recreated my browses and they work as expected in that they obey the skip rule when I turn it on or off. It's just odd that my original browses all did the same thing and I never got them to work - the IDfield remained hi-lighted .. but the new browses work now. I do have one other browse based on a set and that is still "broken" so I will try to use an expression in there and will let you know.
                Thanks, Mark

                Comment


                  #9
                  Re: Custom Browse Not skipping Field as set in Rules ( later on)

                  I pretty much recreated my browses and they work as expected in that they obey the skip rule when I turn it on or off. It's just odd that my original browses all did the same thing and I never got them to work - the IDfield remained hi-lighted .. but the new browses work now. I do have one other browse based on a set and that is still "broken" so I will try to use an expression in there and will let you know.
                  Thanks, Mark

                  Comment


                    #10
                    Re: Custom Browse Not skipping Field as set in Rules ( later on)

                    I looked at your example Ted (thanks!) and did modify the skip rule to a different expression - device_id>0, but the browse doesn't skip the field, just highlights it ..,oh well I don't know what I did when I originally created these browses, but I'll just recreate. Thanks for your help everyone. -Mark

                    Comment


                      #11
                      Re: Custom Browse Not skipping Field as set in Rules ( later on)

                      Well, after much gnashing of teeth, I finally got a similar result to yours Mark.
                      I created a Set with the first field set to auto increment and skip = .t. and also tried field non blank.

                      Created a Browse based on the Set.
                      When the Browse is opened, the Skip doesn't fire. It does fire however when entering a new record or when you go to the next record though.
                      This doesn't happen with a Form however and the rules apply from the form being opened.
                      See our Hybrid Option here;
                      https://hybridapps.example-software.com/


                      Apologies to anyone I haven't managed to upset yet.
                      You are held in a queue and I will get to you soon.

                      Comment

                      Working...
                      X