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
Devcon 2020 Goes Virtual! LEARN MORE >

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

This is NOT how it should be

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    This is NOT how it should be

    In desktop, you can set up a field in the field rules to be a lookup of another database. That field rule can also populate other fields. This works great and I have used it often. However in V11 Server, this does not seem to work as well. Users, for the most part, want to make their input of information fast and easy, especially if there is a lot to do!

    So maybe I never noticed this before, but I have a grid with a detail section. One of the fields in the detail section is called "Actcode" which is a two letter code, which in turn looks up another dbf and fills in various fields. The issue(s) is/are this. If the user types "pu" (small case) in the lookup field, there is no warning and the input is accepted, even though that two letter form exists, albeit as "PU" in the lookup dbf. Somehow in desktop this works ok, but not in the server version. Also, even though I have checked "Honor Field Rules", these rules are not honored, the data of "pu" is accepted and no lookup occurs. Maybe this was some kind of oversight or I never noticed this, but I need to get this to work. In the same vein, I noticed that if I enter "pu" then a dropdown list comes up showing "PU", so I could select that and it will work, but again, a user doing input would most likely miss this. Pointing and clicking each time is cumbersome.

    So, I need to either transform the "pu" to uppercase before the lookup or not allow the user to continue, until a proper selection is made. I can't seem to do either one successfully.

    Also, I reported what I think is a bug, the fact that when using a lookup that contains an image field, that image is not brought over to the new dbf in the lookup. In fact, it returns an error.

    Any other ideas or workaround on this would be most appreciated!

    Charlie
    Tags: None
    #2
    Re: This is NOT how it should be

    I had never noticed this before, always picking from the dropdown list I guess. But yes it is really annoying, the lookup should be case insensitive.

    Comment

      #3
      Re: This is NOT how it should be

      You can try this in the client side OnBlur or OnChange event.
      Code:
      this.value=this.value.toUpperCase();
      Last edited by frankbicknell; 05-12-2012, 09:45 AM.
      Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

      Comment

        #4
        Re: This is NOT how it should be

        transformations.png

        right after i posted, i realized I missed the point. sorry. don't know if this correctly addresses the lookup issue or not...

        Comment

          #5
          Re: This is NOT how it should be

          Sorry Frank. I don't see those events. I have OnRowBlur and OnRowChange???

          Comment

            #6
            Re: This is NOT how it should be

            Originally posted by frankbicknell View Post
            You can try this in the client side OnBlur or OnChange event.
            Code:
            this.value=this.value.toUpperCase();
            That should say You could try this in the 'Fields JavaScript Event', sorry.
            Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

            Comment

              #7
              Re: This is NOT how it should be

              The problem with setting the input to always return uppercase is your lookup data would need to be uppercase as well.

              The question is why is a lookup field case sensitive? I use a company name lookup in several places and I do not store the company name in either upper or lower case, it is mixed to match the companies registered name. If you have say Alpha Software, and alPha soFtWare in your list of companies, there is always an option to add something else to differentiate between the two if the user would be unsure which is the one he needs.

              Comment

                #8
                Re: This is NOT how it should be

                It might make sense to you, but it is not the way apps should work! alpha software and ALPHA Software are two different companies in database terms. It needs to be resolved by the programmer. This could be done with a number field or id number, for example, but the problem remains. In any event, this is not how the desktop version works, so it should be the same in the server version.

                Comment

                Previous template Next
                Working...
                X