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

Set Primary Address

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

    #16
    Re: Set Primary Address

    Also tried

    IF cn.open("::Name::JAC")=.f.
    alert("boken")
    else
    vSQL = "update email SET isActive = 0 WHERE fk_trainee_id ="+e.dataSubmitted.fk_trainee_id
    cn.execute(vSQL)
    end if

    But I do not get an alert and the records do not update. Im seriously at a loss at this?

    Comment


      #17
      Re: Set Primary Address

      Take your sql statement and try running it in whatever you are using to run SQL statements. (ie: Navicat or SQL server manager.)

      Make sure you have a working sql statement. Because what you are describing is acting like the sql is not running properly.

      Also, you should put in

      debug(1)

      At the front of this code.

      That will put you into debugger mode. The next thing to check is that fk_trainee_id is holding the correct information.

      From the debugger, you can see all the variables. If you've never been in the debugger, you are in for a treat!

      Larry

      Comment


        #18
        Re: Set Primary Address

        Im pretty sure Im using the debug(1) wrong because for every variable that I dimmed, it tells me that the variable is not found. Need to research how to use the debug(1) statement.

        Comment


          #19
          Re: Set Primary Address

          Start stepping through the procedure, at least until you get past the dims.

          Until you actually encounter the dim, it won't be there.

          The debugging starts right at the debug command and any statements that come after it haven't been run yet.

          Comment


            #20
            Re: Set Primary Address

            Ok, I Just stepped through my statement and everything looks fine, Everytime the step gets to a flag, it returns .t. Heres the statement I am running

            debug(1)
            dim cn as sql::Connection
            dim TraineeID as n
            dim sqlUpdate as c
            TraineeID = e.dataSubmitted.FK_TRAINEE_ID

            flag = cn.open("::Name::JAC")
            If flag = .f. then
            alert("Could Not Establish Connection")
            end if

            sqlUpdate = "UPDATE email SET isActive = 0 WHERE fk_trainee_id="+TraineeID

            flag = cn.Execute(sqlUpdate)

            And it is using the correct Parent ID. But the update never happens? What am I missing.

            Comment


              #21
              Re: Set Primary Address

              I ran

              UPDATE jac.email SET isActive = 0 WHERE fk_trainee_id=8064

              In MySQL workbench (I use navicat but Im not sure how to run a query through it) and the result was zero rows affected, but there are atleast five that it should have updated?

              Comment


                #22
                Re: Set Primary Address

                Ooops, My bad.

                Ive been refreshing the wrong table which is why I never saw the change, I am so sorry for wasting your time. The update is working just fine.

                Comment


                  #23
                  Re: Set Primary Address

                  Two more questions, there is a date field which I would also like to update called "ModifiedOn" which simply holds a date in the following format 'MM/DD/YYYY', When I try to add this column to the update as Date(), it returns all zeros in MySQL table. Do I need to format this before it will insert the properly formatted date?

                  How do I create a pop-up window for the user if the update failed? alert() does not work here,
                  flag = cn.Execute(sqlUPDATE)
                  If flag = .f. then
                  alert("Record Update ERROR")
                  end if

                  Comment


                    #24
                    Re: Set Primary Address

                    alert is a javascript function, not an Xbasic function. Look in the instructions for the event you are in to get an explanation of how to run javascript after the event.

                    Generally, you have to do something like:

                    e.javascript = "alert('Record Update Error');"

                    Note the exact format of what I put in there. Capitalization and formatting matter a LOT for javascript. Also, single quotes denote text in JavaScript, but double quotes are text in Xbasic.

                    As far as the modified on date - just do that in a trigger:

                    set modifiedon = date(now()) ;

                    In the update and/or the insert trigger.

                    Comment


                      #25
                      Re: Set Primary Address

                      Originally posted by lgrupido View Post
                      alert is a javascript function, not an Xbasic function. Look in the instructions for the event you are in to get an explanation of how to run javascript after the event.

                      Generally, you have to do something like:

                      e.javascript = "alert('Record Update Error');"

                      Note the exact format of what I put in there. Capitalization and formatting matter a LOT for javascript. Also, single quotes denote text in JavaScript, but double quotes are text in Xbasic.

                      As far as the modified on date - just do that in a trigger:

                      set modifiedon = date(now()) ;

                      In the update and/or the insert trigger.
                      Thank you Larry, right before you posted this reply I found another thread that mentioned using args.set() with dim args as sql::Arguments which I had some time to play with and turned out to work just fine.

                      I didnt know you could inject javascript into the xbasic command, Thank you for the e.javascript = "alert('Record Update Error');" I will put that in and see where I end up.

                      - Ivan

                      Comment

                      Working...
                      X