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

Updating fields

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

    Updating fields

    In an application that we recently started running, there is a field that pulls the prefix, first name, and last name from thier respective fields and combines them for use in reports. For instance.....

    PREFIX: Mr.
    FIRSTNAME: John
    LASTNAME: Stevens

    WHOLENAME: Mr. John Stevens

    The field rules are set to update when tabbed to, or on save if not touched.

    My problem is this. If a user makes an error in the spelling of any part of the name and saves the record, the WHOLENAME is also spelled wrong. When the user goes in and changes the spelling, I can't figure out how to get the WHOLENAME field to update.

    Any suggestions?

    Thanks in advance.

    John

    #2
    RE: Updating fields

    John,

    There are two approaches I can think of for solving this. The first is to set the field rules in salutation, last, and first name to update fullname by posting the new value combinations whenever they are changed. The second way would be to program the record on change event with code to rewrite the fullname whenever the record gets changed and triggers the OnChange event.

    Dave

    Comment


      #3
      RE: Updating fields

      John

      Would another solution be to not have a calculated field in the table but place it on the report. That way the calculation is automatically generated each time the report is run?

      Regards

      Glen
      Glen Schild



      My Blog

      Comment


        #4
        RE: Updating fields

        make a calc field on the report as suggested:
        expression:
        alltrim(salution)+" "+alltrim(firstname)+" "+alltrim(last)

        Comment


          #5
          RE: Updating fields

          You will have to excuse my inexperience. I am not a programmer, although I play on here at work. We hired a consultant to write this application, but he is unwilling to help us resolve this issue. I know enough about programming to be dangerous and can put code in if I know the code.

          Could you help me with this? I like the first suggestion.

          John

          Comment


            #6
            RE: Updating fields

            John,
            Is "wholename" a concatenated, calculated field?
            efs

            Comment


              #7
              RE: Updating fields

              Yes it is, but no it's not.

              But...I think I found the answer to my problem.

              The field WAS a "user entry" type field, and had a field rule to calculate the data when the field was entered, or when the record was saved if the field was not touched.

              What I think seems to be working is to make it a calculated field with an expression. This seems to update the field as soon as a change is made to any other field IMMEDIATELY!!!!

              My question....will this cause any other problems that I am not currently seeing?

              John

              Comment


                #8
                RE: Updating fields

                John,

                The best method was suggested earlier, make it a concatenated,
                calculated field at report level. I also notice that you might need a
                middle initial. assuming the following:
                Salutation is Mr. Mrs. or Ms
                F_name is for first name
                Midinit is for the middle initial
                L_name is last name

                The concatenated calc field would look like this:

                if (isblank("midinit"),alltrim(salutation)+" "+alltrim(F_name)+" "+
                alltrim(L_name),alltrim(salutation)+" "+alltrim(F_name)+" "+midinit+
                ". "+alltrim(L_name))
                efs

                Comment

                Working...
                X