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

Browse Property and Object Explorer settings both fail

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

  • Browse Property and Object Explorer settings both fail

    Has anyone successfully been able to remove the title from a browse, which is used in a field lookup?

    If for any reason, the title can not be removed, can the its font and size of be customized?

    As explained in a companion posting, I am trying to replicate the appearance of a native A5V9 combo box’s display of a list of values when a table lookup is used in a field rule.

    As documented in that posting, A5V9’s displays list values differently depending on whether the data source is user entered values or values from a table.

    I would like to have a more consistent appearance, and over the weekend, attempted to compensate for this shortcoming by using a custom browse.

    Below are two significant snags that I encountered:

    Screen 1 shows a simple browse in design mode where the title font
    is set to Tahoma 16 point.

    Screen 2 shows that browse in view mode. Note that as expected the
    title indeed is Tahoma 16 point.

    Screen 3 shows that the browse “brwLookup” is assigned to the field rule
    Lookup tab for field “Telephone_type”.

    What do you think the browse for the lookup field will look like on the form?
    Do you expect that the title will be Tahoma 16 point?
    Wouldn’t that be reasonable?

    Screen 4 shows a form with the field and its Lookup browse. Sure doesn’t look like what we saw in design mode.

    What happened to the Tahoma font? A5V9 has overwritten it.
    What happened to the 16 point size? Again A5V9 has overwritten it.

    OK, now let’s use the Object Explorer to change properties. My original goal was to replicate the appearance of a native A5V9 combo box in the display of multiple values. You may remember that a combo box does not have a title, just a list of values. So let’s use the Object Explorer to remove the title.

    Screen 5 shows the browse in design mode and the property “Show titles” is initially set to True.

    Screen 6 shows the browse in design mode after the “Show titles” property is changed to False. Also note that the title indeed no longer appears at the top of the list.

    What do you think the display of the browse will look like?
    Would you expect that just the list of values would be displayed with no title?
    Wouldn’t that be reasonable?

    Screen 7 shows that despite clicking the Set button and the save button, the browse is displayed with a title.

    What happened to the “Show titles” property?
    If you go back into design mode, you will see that A5V9 has overwritten False with True.

    One last question: because a combo box does not have buttons, I would like to remove the button from a browse? I can’t seem to find a property that allows this to be done. Is it possible?

    Bob McGaffic
    Pittsburgh

  • #2
    Re: Browse Property and Object Explorer settings both fail

    Hi Bob,

    Here is (yet another!) possible work a round....I only tested from a form however but possibly could work in your situation. Placing script on some event that is triggered when the lookup is performed (maybe the OnTimer event of the form?), you could set the Window Title to " ". Don't know if the browse properties are even available to change in your circumstance (unless open and hidden??).

    :Explicit_Browse_Name.Window_title =" "

    I can hear what you're thinking BTW!! Why is a work a round even needed!!? Shouldn't be...but at least, most times, a work a round can be created in Alpha.

    In lieu of a better approach, hopefully this will be of some help.
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


    • #3
      Re: Browse Property and Object Explorer settings both fail

      Mike,

      Thanks for another way to skin the cat!

      I tried your suggestion as follows:

      For the field with the field rule for a lookup:

      Code:
      On Arrive event
      :brwLookup.Window_title = ""
      A separate browse exists called brwLookup.

      When I click on the field the following error message is encountered:
      No found
      :brwLookup not found

      If I remove the :, then the display is as before, namely, the title is displayed and no error message is received.

      Maybe the alternative question should be asked:

      Where in A5V9 is the "default browse" defined for field rule lookups? Can this default be modified? Interestingly, the default browse has no title!!!

      My problem with the default browse was the indentation and wrong font.
      Not to mention trying to see a black checkmark on a dark navy background. Alpha must expect users to have the vision of eagles or they simply don't care whether something is easy to read or not. This lack of attention to detail is driving me crazy!!!

      This kind of putzing around greatly diminishes A5V9 usefulness as Rapid Application Development environment.

      Bob McGaffic
      Pittsburgh
      Last edited by rmcgaffic; 07-21-2008, 12:52 PM.

      Comment


      • #4
        Re: Browse Property and Object Explorer settings both fail

        Hi Bob,

        Again unsure if you can use it but I could not get "" to work but making the title equal to a space did " " . Just making sure you tried it this way.
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


        • #5
          Re: Browse Property and Object Explorer settings both fail

          Mike,

          I changed the "" to " " and the error remains.

          My code for On Arrive event is now

          Code:
          :brwLookup.Window_title = " "
          were brwLookup is the name of a browse.

          Were you able to get your code to work with a field rule lookup and the on arrive event?

          Thanks,
          Bob McGaffic
          Pittsburgh

          Comment


          • #6
            Re: Browse Property and Object Explorer settings both fail

            Bob,
            No go for me on this. I can change a named browse's title from events, but cannot change the lookup dialog's whether it uses the default or a named browse as its source. I'll check the registry as sometimes these types of things are located there but not expecting to find a solution.
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


            • #7
              Re: Browse Property and Object Explorer settings both fail

              Mike,

              You are obviously more tech savvy than I am. I have generally been advised to stay away from the registry.

              Bob McGaffic
              Pittsburgh

              Comment

              Working...
              X