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

Missing browse properties?

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

  • Missing browse properties?

    Is there someplace other than Browse>Properties and Object Explorer that would allow a browse to have the same appearance whether it is imbedded or not?

    I would like to hide the row selector for a browse, that is the little button at the left of the browse.

    I see how this is possible when an embedded browse is used since the following properties are available for use:

    Vertical lines
    Horizontal lines
    Parent records only
    Vertical scroll bar
    Hortizontal scrollbar
    Highlight row
    ROW SELECTOR
    Column titles

    This property works just fine. When I place a browse on a form, I am able to hide the row selector button.

    But when I create a browse via Browse>Design, I find only the following settings:

    Vertical lines
    Horizontal lines
    Parent records only

    What happened to the other properties? I looked in View>Object explorer and can not find them there either.

    I would think that whether a browse is imbedded or simply displayed independently of a form, that the properties would be the same.

    Bob McGaffic
    Pittsburgh

  • #2
    Re: Missing browse properties?

    Bob

    You could use xbasic code in the form's oninit or onActivate event

    Code:
    :formname:browsename.showrowselector=.F.
    That does show up in Object explorer.

    Tom

    Comment


    • #3
      Re: Missing browse properties?

      Tom,

      I tried your suggestions and unfortunately found that it does not work for a non-embedded browse.

      The code does work with an embedded browse placed on a form, but the browse I am using is that for a table lookup for a field rule.

      Select table>Edit field rules>Select field>Click on tab Lookups>Select table lookup>Browse layout to: ENTER YOUR BROWSE NAME HERE

      This this browse is only called when the user clicks on the little downward arrow which is displayed when the field receives the cursor.

      In my mind a browse is a browse. I can't understand why an embedded browse would have more properties (including rowselector property) than the browse itself. Am I missing something? What design objective is served by having different properties depending on whether a browse is embedded or not?

      Bob McGaffic
      Pittsburgh

      Comment


      • #4
        Re: Missing browse properties?

        Hello, Bob.

        I suspect that internally the browse object is very different from the browse layout.

        Judging from message board traffic over the last 7 or 8 years I also suspect that the browse layout is meeting the needs of Alpha's customers, even though it's not as customizable as the browse object (control).

        When customizing is needed it's dead simple to drop a browse object on a form and use the form instead of a saved browse layout.

        -- tom

        Comment


        • #5
          Re: Missing browse properties?

          Originally posted by rmcgaffic View Post
          I can't understand why an embedded browse would have more properties (including rowselector property) than the browse itself. Am I missing something? What design objective is served by having different properties depending on whether a browse is embedded or not?
          Bob, I think Tom is right. They are both "browses", yet different. I'm not disagreeing w. your premise, but it is what it is. (or, more precisely, they are what they are)


          Originally posted by Tom Cone Jr View Post
          Judging from message board traffic over the last 7 or 8 years I also suspect that the browse layout is meeting the needs of Alpha's customers, even though it's not as customizable as the browse object (control).
          errrr, eeehhh...that might be somewhat debatable...

          When customizing is needed it's dead simple to drop a browse object on a form and use the form instead of a saved browse layout.
          True. But one advantage that I have found for a free-form browse is when you need to display a lot of fields and a lot of records, you can maximize the browse and take advantage of the available real estate.

          Also note that Bob is using the browse for a table lookup.
          Peter
          AlphaBase Solutions, LLC

          Peter@AlphaBaseSolutions.com
          https://www.alphabasesolutions.com


          Comment


          • #6
            Re: Missing browse properties?

            Peter, I searched the Wishlist Forum for posts relating to "browse" and "properties". Got 12 hits, extending back to early 2005. All but one were talking about embedded browses. Doesn't seem to me that the natives are clamoring for improvements to the browse layout. -- tom

            Comment


            • #7
              Re: Missing browse properties?

              I've attached a screenshot below from Alpha Sports that shows that Alpha Five Version 8 permitted field rule lookups based on tables that did not display the row selector button. Whether the field was a type in field or a field in a browse, the row selector button does not appear when the list of available values is displayed.

              I was disappointed that Version 9 was a step backwards in that the field rule lookup mandates the display of the row selector button where it did not in Version 8.

              At the suggestion of several forum members that I use a browse layout to achieve what Version 8 made so effortless, I did exactly that. After identifying 5 bugs in the process, which Alpha corrected in a near-flash, the only issue remaining is the removal of the row selector button.

              If I can just hide the row selector, I can achieve the appearance of Version 8, and by the way, achieve a consistency in appearance for all Version 9 lookup displays, regardless of whether from a combo box table lookup or field rule table lookup.

              Is this a situation that what the left hand of Alpha gives, the right hand of Alpha takes away?

              Bob McGaffic
              Pittsburgh

              Comment


              • #8
                Re: Missing browse properties?

                ...Got 12 hits...
                Not sure about your count, but I remember dozens of complaints pre 2005, I think. Mostly about not being able to control the browse window title. There were many other complaints affecting both browse types - most, or all, of which have been addressed in v9, I believe.
                Peter
                AlphaBase Solutions, LLC

                Peter@AlphaBaseSolutions.com
                https://www.alphabasesolutions.com


                Comment

                Working...
                X