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

do not display placeholder

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

    do not display placeholder

    If the field in a record contains a placeholder character ~ I want the form not to display the character. Either remain blank or replace with text "not listed".

    Thought I could add an "on arrive" event to the form field and check for the ~ placeholder character, then replace ...

    Code syntax ...?

    #2
    RE: do not display placeholder

    If you are speaking of the placeholder character in a mask, you will probably need to define a form level calculated field (or report level, etc) something like

    if(alltrim(Id)="","Not listed",mask(alltrim(id)," ~ "))

    where id is the table field having the mask and the mask string in the calculated field definition matches the data entry mask using spaces. IOW if the field rule mask were

    (000) | 000-0000

    the calculated field rule mask string would be

    "(__)_|___-___"

    using underscores in place of spaces for demonstration.

    The field rule should have the checkbox "Do not store mask
    iterals in field" is selected.

    Screenshots attached.
    There can be only one.

    Comment


      #3
      RE: do not display placeholder

      Another method that I often like to use is to build my own function that will enter the mask "after the fact". This function is then used in the CanWrite event of the field. BUT, the big advantage is that it can also be used in custom lookups where I prompt the user for a value then format the input value as needed for the lookup.

      For the situation in question, the result would be that no 'placeholder' characters would be entered unless there was actually a value in the field.

      For example, I have a function called Phone_Dash() that outputs phone numbers as either NNN-NNNN or NNN-NNN-NNNN. (Longer numbers end up as NNN-NNN-NNNNNNNNN.)

      I don't care how the user inputs the number. It can be 234-567-8900 or 2345678900 or 1 (234)-56789-00 or even 1-2-3-4-5-6-7-8-9-0-0. It still comes out as 234-567-8900. (Note that my function even removes the preceding "1".) Of course, the most common input is the easiest - 2345678909.

      This method is very flexible. In my case, if the value entered is blank or less than 3 characters, no dashes are added but any special characters will be removed. It also warns the user if any letters are entered. Other features could easily be added - it's just a function so it does whatever I define it to do.

      In the CanWrite event, I simply add:
      A_field_value = phone_dash( A_field_value )

      In a custom lookup I might use something like:

      phone_in = ui_get_text( "PHONE NUMBER", "Lookup what number?" )
      IF phone_in = ""
      END'
      END IF
      phone_in = phone_dash( phone_in )
      Tbl_Pointer.fetch_find( phone_in )
      ....

      (Actually, today I'd probably end up with something much more elaborate in an xdialog but I won't go there - to complicated for demo purposes.)

      Cal Locklin
      www.aimsdc.net

      Comment

      Working...
      X