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



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

Make Textbox uneditable by user

  • Filter
  • Time
  • Show
Clear All
new posts

    Make Textbox uneditable by user

    I have three text boxes in a grid that I want the user to see, but not be able to edit. These are fields that are tracking who the user is, when they added/edited, and what company they are with.

    I have attempted to set these fields in the server-side CanUpdateRecord and CanInsertRecord events with the DataSubmitted script. The problem with the DataSubmitted method is that the fields have to be Textboxes, not Labels, and the cannot be unchecked in the Updateable property. Therefore, the user is able to change the data in which I only want him to see, not edit.

    I am sure it is something simple such as locking, but I can't find.


    Re: Make Textbox uneditable by user

    Try setting the Enable Expression of the text box to 1=2
    Carol King
    Developer of Custom Homebuilders' Solutions (CHS)


      Re: Make Textbox uneditable by user

      Worked perfect.

      Thank you Carol.


        Re: Make Textbox uneditable by user

        If it is a label and not set to updateable, it will not be updateable and you do not need to have any code to handle it. Is there some other reason you cannot use a label?

        If it is an updateable textbox, it is possible that a changed value will be submitted to the server, regardless of the enable expression, so you must have code to discard any changed values before committing anything. This is something that is possible to do, but the label is a much simpler and more fool-proof solution.

        Lenny Forziati
        Vice President, Internet Products and Technical Services
        Alpha Software Corporation


          Re: Make Textbox uneditable by user

          I am probably going to expose my ignorance here but...

          I do not see an Updateable property for a Label that can be set. As I stated in my first question, once the field is changed to a Label, it is no longer available to be set using DataSubmitted on the Server-side Events. I also discovered the same result if you take a TextBox and uncheck the Updateable property.

          Since these fields are basically just an audit trail for who changed it and when, I want the values updated anyway anytime the form is dirty. Therefore, you are correct in saying the values are sent to the server even though the field's Enable Expression is set to 1=2. This is the way I want it to work in this instance.

          I certainly could be missing something though, newbie and all.


            Re: Make Textbox uneditable by user

            No, it was I that missed something. I did not understand that you wanted the fields to be updateable, I thought you wanted them totally locked down.

            My other point still remains though - make sure your server-side code does not trust the value submitted for these fields. While having an enable expression that is always false makes it slightly less convenient to submit an arbitrary value, it is far from impossible to do so. This means your event code should always discard whatever is passed in and set the value using some other logic.

            Lenny Forziati
            Vice President, Internet Products and Technical Services
            Alpha Software Corporation