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

dirty column

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

    dirty column

    i have a field which has its value set in the DialogValidate event

    Code:
    if e.DataSubmitted.client1 = "None" .and. e.DataSubmitted.client2 = "None" then
    		e.control.completed = "Completed"
    	else
    		e.control.completed = "Not Completed"
    	end if
    i have made the field dirty in the afterdialogvalidate

    Code:
    e.dirtyColumns = e.dirtyColumns + crlf()+ "COMPLETED"
    the correct value shows in the field once the submit button has been pressed but the value isnt being sent to the table.

    can anyone let me know what i need to do or where i can find out. i have looked at a video making fields dirty but doesnt seemed to have helped.

    #2
    Re: dirty column

    In your afterDialogValidate event, do you have

    Code:
    ExecuteServerSideAction("Save Data::Save")
    to save the data?

    I wonder what the difference is between using e.datasubmitted.controlname = "value" and e.control.controlname = "value". Both work in setting the value of the named control.

    Comment


      #3
      Re: dirty column

      yeah, i have the dialog saving the data.

      all i need to do is set the value of a field in a related table based upon a users choice, i thought this was the right way to do it. any ideas?

      Comment


        #4
        Re: dirty column

        Using a MySQL table, I've found the same thing... the code you post does not change the table data.

        Adding the following statements saves the data as well. Works here... hope it works for you.

        Code:
        if e.DataSubmitted.client1 = "None" .and. e.DataSubmitted.client2 = "None" then
                        e.datasubmitted.completed= "Completed"
        		e.control.completed = "Completed"
        	else
                        e.datasubmitted.completed= "Not Completed
        		e.control.completed = "Not Completed"
        	end if

        Comment


          #5
          Re: dirty column

          david, thanks for helping, but this still isnt updating my table (.dbf). the control is set correctly but the data isnt being saved.

          lots of people must be setting and saving values, anyone want to share how your doing it?

          Comment


            #6
            Re: dirty column

            Can you zip your table and your dialog and post it here? Then I can see exactly what's happening... it would really help.

            Comment


              #7
              Re: dirty column

              i have zipped the table that i am having trouble saving data to. there is a related table 1:1 but i cant zip this tonight as it has all client data in it. there is only a couple of fields in the dialog from the main client table.
              Attached Files

              Comment


                #8
                Re: dirty column

                Hey Richard,

                I think you sent through an older dialog... it's not a dialog2 dialog... it's a dialog dialog - yikes... this is like the iPad 3...errr, the new iPad...

                Is this the right one?

                Comment


                  #9
                  Re: dirty column

                  sorry, that was the old one from v10 (which worked fine). correct one now attached.
                  Attached Files

                  Comment


                    #10
                    Re: dirty column

                    No idea why... but this fixes the problem... on my system anyway... I hope it does on yours... this is the sort of things you spend so much time on... and for what.

                    Add a crlf() to the end of your e.dirtyColumns statement... sheesh.

                    Code:
                    e.dirtyColumns = e.dirtyColumns + crlf() + "COMPLETED" + crlf()
                    Other stuff that got in your way is that your e.dirtyColumns statement appears AFTER your Action script for saving the record. Move this statement so that it executes BEFORE the save... otherwise the save cannot act on the changed control.

                    I hope that does it for you.

                    Comment


                      #11
                      Re: dirty column

                      David,

                      Thanks for your help, this worked for me. i then tried without the additional '+ crlf()' on the dirtycolumns and it still works. it must have been the positioning of the dirtycolumns code which i had put after the savedata function.

                      My app requires lots of validation like this, so this helps me a great deal.

                      thanks again.

                      Comment


                        #12
                        Re: dirty column

                        I just re-tried on my system and it also works without the extra crlf()... so that's good. Sheesh... looked at the data so many times.

                        Comment

                        Working...
                        X