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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Dialog2 bug when saving data with datetime primary Keys

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Dialog2 bug when saving data with datetime primary Keys

    Hello,

    When the updateable data is defined via primary keys using datetime datatype, there might be a bug when you use the serverside action scripting to save data in a dialog2 component.

    Look at this simple case : I define a table in my SQL, the three first fields are primary keys, second and third fields are datetime data.
    Then, I use the onDialogInitialize event combined with the action scripting to populate my fields. It works normally (see second and third screenshots).
    To be able to save the textbox after user updates, I inserted the "save submitted data to tables" action scripting in the afterDialogValidate event. But I get the error showed on screen 4 after pushing the submit button. Look at the SQL log, the third primary key querrying the database is wrong ! If it is a problem of data format in PKs definition in the action scirpting, I can't understand why the populate action works and not the save action ...

    I made the same test with a table using also three PKs but using only INTeger datatype and there is no error. I am currently using build 3828.

    I am new user. It this a bug ? Can anybody confirm it ? Have I missed something ? Thanks a lot !


    Dialog2 bug 0.jpgDialog2 bug 1.jpgDialog2 bug 2.jpgDialog2 bug 3.jpg
    Tags: None
    #2
    Re: Dialog2 bug when saving data with datetime primary Keys

    Have you got your other fields in the dialog? They are not shown in your screen shots, if not put them on to make sure the data is going to the correct variable when you initialise

    Comment

      #3
      Re: Dialog2 bug when saving data with datetime primary Keys

      Hello Lance,

      I just made the test with the key fields shown in the dialog screen (see attached). I have no issue to populate the dialog, but again, when trying to save, it seems there is a problem with the third primary key field.

      Dialog2 bug 4.jpgDialog2 bug 5.jpg

      Comment

        #4
        Re: Dialog2 bug when saving data with datetime primary Keys

        I tried it and got exactly the same, but suspect it is some issue with primary keys

        Comment

          #5
          Re: Dialog2 bug when saving data with datetime primary Keys

          I get exactly the same results. The 1st and 2nd keys are good... the 3rd key comes through as 0000-00-00 00:00:00 0000

          It doesn't matter if you change the key data or not.
          And... this only happens if you "load data" first and only with a Datetime field.

          If I start with a new record, the record gets written to the database with correct date time information (well... date information anyway - the time is zero)... no errors.
          If I use a DATE field instead of DATETIME then all is good... loading and writing.

          So, it looks as if there's an issue with how DATETIME is being worked with.

          Comment

            #6
            Re: Dialog2 bug when saving data with datetime primary Keys

            this is a bug. it is fixed now. the fix will be in the next update. if you require a pre-release of the update, please let me know.

            Comment

              #7
              Re: Dialog2 bug when saving data with datetime primary Keys

              I've been having a similar problem. See: http://msgboard.alphasoftware.com/al...ith-two-tables

              I'm not using datetime's, but I do have two primary key's in a second table in the dialog2. I've updated to 2247-3829 (The unreleased patch). And I'm still having the same error.

              Comment

                #8
                Re: Dialog2 bug when saving data with datetime primary Keys

                the pre-release update won't have the fix in it till tomorrow morning. the fix was just submitted this morning.

                Comment

                  #9
                  Re: Dialog2 bug when saving data with datetime primary Keys

                  If at all possible, I'd like to see If I could get the pre-release patch. I'm hoping to go live with my new version 11 components on Monday.

                  Comment

                    #10
                    Re: Dialog2 bug when saving data with datetime primary Keys

                    please send me an email with your email address and i will send you links

                    Comment

                    Previous template Next
                    Working...
                    X