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

Field Editing

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

    Field Editing

    Is there an easy way to make an individual field non-editable once it has been created while still allowing other fields to be changed?

    #2
    RE: Field Editing

    Where do you want to make it noneditable?

    On a form you need only go to properties (of the displayed field) and make it read only. In a browse, select the column for the field and likewise select properties, read only.
    There can be only one.

    Comment


      #3
      RE: Field Editing

      Another suggestion is to set a field rule that makes it skip the field if it isnotblank.
      Terry

      Comment


        #4
        RE: Field Editing

        By "Once it is created" I assume that you mean you can change the record as long as you are in the add mode. Try a field rule on the canwrite event for that field and only allow changes when you are in the add mode.

        Comment


          #5
          RE: Field Editing

          If it is read only then I can not enter a value in the first place at data entry stage.

          Long story short at night a novice user is accidentally typing over fields. What I want to do is; Once data is entered by a person I want it read only at that point.

          Comment


            #6
            RE: Field Editing

            Bruce, you might try changing the data entry field rule so that the cursor is positioned at 'end of unselected text'. An accidental keystroke will not displace the previous text in the field, yet the user can edit existing values whenever they want to.

            Comment


              #7
              RE: Field Editing

              You could make the fields read only and then place a button on the form that allows changes. At least an intentional action is necessary to make any changes.

              Comment


                #8
                RE: Field Editing

                Terry; I am trying to do just that more or less but can't get the expression builder to accept what, to me, looks perfectly logical.

                In the "Skip" expression I say "isblank(Home_State_Region)"
                and it says "! No Such Field" but I just pasted the field name in using the expression builder. Being a lousy typist I figure it's faster.

                What I am trying to do is to bypass the city and state through and let the user input the zip using the zipcode database to validate and fill in the city and state.

                I suppose I could let the user enter city etc and fill in the reat but I am still stuck. I also want to have the city editable afterwards because the zipcode database doesn't have every city correct. Sometimes it has the Major city not the suburb I actually want.

                Comment


                  #9
                  RE: Field Editing

                  Skip,
                  I think the field name needs to be in quotes inside the parens:
                  isblank("Home_state...")
                  Pat Bremkamp
                  MindKicks Consulting

                  Comment


                    #10
                    RE: Field Editing

                    Skip,

                    "isblank(Home_State_Region)"

                    should be: isblank("Home_State_Region")

                    the field name needs to be quotes

                    Comment


                      #11
                      RE: Field Editing


                      Stupid of me - The field should be in quotes shouldn't it ... Should have read the rest of the forum ...

                      Sorry about that. Thanks for the answers that are on the way :-)

                      [%-{)>
                      T-Rex

                      Comment

                      Working...
                      X