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

highlighted fields

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

    highlighted fields

    Hi, apologies for what I'm sure is a simple question, but, although I've tried searches, I'm not really sure what I should be searching for.

    I'm moving an application from ver 4.5 to ver 6.00. In ver 4.5 I could modify a record, via a form, and tab from field to field. The first character of a field would be highlighted on entry to the field. In ver 6.00, the whole of the field is highlighted on entry. This may not seem like much of a problem, but often only the first character of the field needs to be changed; if any character is typed in, the whole (highlighted) string is deleted, whereas in ver 4.5 only the first character would be changed.

    I hope this can be rectified by a global set up change, rather than have to trawl through hundreds of fields individually. Can anyone please point me in the right direction?

    Very many thanks,

    Martin.
    (It's Martin Wolff, but I seem to have created a new forum identity in my first name only.)

    #2
    Martin,

    You will find this setting in field rules->data entry->Position Cursor at, which is all the way on the bottom of the page.

    I do not know a way of globally changing a field rule, but someone else might.

    Scott

    Comment


      #3
      Thanks Scott, but the rules are the same as when it was running under ver. 4.5. The problem is not where the cursor is being placed in the field (it's at the start, as it was in the 4.5 version) but the fact that the entire field is highlighted, which seems to mean that any single key press deletes the existing data and overwrites it with that single character. It's exactly the same as if a section of text had been highlighted in, say, Word and then a key had been pressed. The highlighted text would be replaced by the key(s) pressed. This seems to happen throughout the application in ver. 6, although it didn't before. Someone else must have noticed this. Any more ideas gratefully received.

      Thanks,

      Martin.

      Comment


        #4
        Scott has the right idea - if you change the cursor position to "Start of UNSELECTED text" (my emphasis), the cursor will be at the beginning of the value, which will NOT be selected. This means you can press DELETE to delete the first character, and then replace it.

        I checked v4.5 - my character fields were completely selected, but fields with masks (i.e. phone numbers) and date fields did indeed select only the first character.

        I think the new (default) method of selecting the entire text is appropriate for more situations than selecting just the first character. In my 13 years of developement, I've rarely seen a case where the user wanted to replace just the first character of a value.

        Comment


          #5
          Yes, thanks Bill, Scott was on the right track. Looks like I've got an exciting day or two modifying all the field rules! I'd hoped there was some global setting. In fact, has anyone suggested "global" field rules (maybe one set for each field type), which over-ride specific settings, for a future version?

          Thank you both.

          Martin Wolff.

          Comment


            #6
            for "which over-ride specific settings", read "which are over-ridden by individual settings".

            Comment

            Working...
            X