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 Value Won't Save

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

    Field Value Won't Save

    I have a button on form1 which opens form2 which is built on a separate table. I'm using variables to show the camid, first, mi and Last field values. When the form opens, all fields show values from from1.

    When the record is saved, the value in the camid field fails to save, thus the link to the child record is broken. The values from the other 3 fields save and show in the now orphaned child record.

    Here's my code. It was working great for quite some time. Any idea what's causing the camid value not to save on the child record?

    if is_object("NCS")
    NCS.new_record() 'begin new record

    'Assign a value to that record
    NCS:Camid.value = parentform:Camid.value
    NCS:FirstName.value = parentform:FirstName.value
    NCS:Mi.value = parentform:Mi.value
    NCS:LastName.value = parentform:LastName.value


    'Assign value to the local var on the called form (NCS)
    NCS:VarCamid.value = parentform:Camid.value
    NCS:VarFirst.value = parentform:FirstName.value
    NCS:VarMi.value = parentform:Mi.value
    NCS:VarLast.value = parentform:LastName.value


    'Display the called form
    NCS.show()
    NCS.activate()

    else
    Form.load("NCS")
    NCS.new_record()

    'Assign value to that record
    NCS:Camid.value = parentform:Camid.value
    NCS:FirstName.value = parentform:FirstName.value
    NCS:Mi.value = parentform:Mi.value
    NCS:LastName.value = parentform:LastName.value


    'assign value to the local var on the called form
    NCS:VarCamid.value = parentform:Camid.value
    NCS:VarFirst.value = parentform:FirstName.value
    NCS:VarMi.value = parentform:Mi.value
    NCS:VarLast.value = parentform:LastName.value


    NCS.show() 'Display the called form
    NCS.activate()

    End If

    END

    Thanks,

    kenn

    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Field Value Won't Save

    WAG's:
    field type mismatch
    field length mismatch
    field rule interference
    field or form event interference

    Comment


      #3
      RE: Field Value Won't Save

      Ken

      Why do you fill the fields in the new record in the called form AND ALSO assign the same values to variables local to that form?

      I don't recall ever trying to assign values to form level variables in this manner. Instead, once the initial values are in place in the objects on the called form, I would use an event in that form to populate the local variables. Perhaps the called form's OnActivate event?

      -- tom

      Comment


        #4
        RE: Field Value Won't Save

        Hi Tom,

        I mis-spoke. There is no First, Mi or Last fields in the table on which form2 is built; only the linking field. The variables on form2 simply show the First, Mi, & Last for reference. I placed the link field on the form in place of the variable and that solved the problem, or did it?.

        The linking value is now filling in on the table on which form2 is built. However, in the past, the link field always filled in w/o having to put the linking field itself on the form.

        Make sense?

        Thanks,

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment


          #5
          RE: Field Value Won't Save

          Steve,

          Thanks for the SWAGs. There are no field rules, The field itself is 8 characters and the variable is 40 characters by default. Field type shouldn't be an issue since one is a variable and the other a character.

          Other field or form interference? How in the world is that figuered out, other than deleting one field at a time and if that doesn't pan out, the form?

          I did create a new form for as a test and had the same results.

          kenn
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment


            #6
            RE: Field Value Won't Save

            >>

            I'm glad you solved the problem, but I was not referring to the variables, they've really nothing to do with it. Changing a viriable on a form will not even put the form into change mode. I was referring to the code above which appeared to enter values directly into the form and should have worked.....unless some event or rule were interfering. You should not have to delete fields to run down errors of this type, simply check your field rules for the field and any events you've coded for the form or for this field. You did indicate that the other fields were being saved correctly and only this field failed. Thusly, one might suspect incorrect object names, field mismatches, rules, or events. It doessn't mean that's the problem; it just means those are a good place to start looking. I've had to do it a hundred times.

            Comment


              #7
              RE: Field Value Won't Save


              Ken, no. Sorry. You're skipping too many steps for me to follow.

              I suggest you dig out my example of Passing Values Between Forms in the Code Archive and look it over. There are three different ways to do what you want, none of which require that the link field actually appear on the called form. What's vital is that the correct value be assigned to the link field in the called form's table at some point before the user saves the record and closes the form.

              -- tom

              Comment


                #8
                RE: Field Value Won't Save

                Tom,

                That's what I thought so I'll have a look.

                Thanks,

                kenn
                TYVM :) kenn

                Knowing what you can achieve will not become reality until you imagine and explore.

                Comment

                Working...
                X