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

update Query not working?

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

  • update Query not working?

    Hi,
    I was trying some code in the afterUpdate Event of the grid.
    But i am not getting the desired result.
    can anyone tell me how to use a debugger in the afterUpdate Event of the Grid
    Please help!!

  • #2
    update Query not working?

    hi everyone below is my code in the afterUpdate event.....
    Code:
    Dim cn as sql::connection
    Dim sqlCommand as c
    DIM args as sql::arguments
    dim rs as SQL::ResultSet
    dim count as n
    dim flagResult as l 
    
    cn.open("::Name::Intranet")
    
    cn.PortableSQLEnabled = .t.
    
    
    sqlCommand = <<%longstring%
    select count(imCustomer.nUnitIDFK) as Count from imCustomer imCustomer 
    INNER JOIN imOperationalMIS
    ON imCustomer.nCustomerID = imOperationalMIS.nCustomerIDFK
    where imOperationalMIS.nOperationalMISID = :ID
    
    %longstring%
    
    args.add("ID", convert_type(e.OldDataSubmitted.nOperationalMISID,"N"))
    
    cn.BeginTransaction()
    
    cn.Execute(sqlCommand, args)
    rs = cn.ResultSet
    count = convert_type(rs.data("Count"),"N")
    
    cn.CommitTransaction()
    
    
    if count <> 0 then
    
    sqlCommand = <<%txt% 
    UPDATE imOperationalMIS SET imOperationalMIS.nUnitIDFK = imCustomer.nUnitIDFK FROM imOperationalMIS INNER JOIN
    imCustomer ON imOperationalMIS.nCustomerIDFK = imCustomer.nCustomerID where imOperationalMIS.nOperationalMISID = :ID
    %txt%
    
    args.set("ID", convert_type(e.OldDataSubmitted.nOperationalMISID,"N"))
    cn.BeginTransaction()
    
    cn.Execute(sqlCommand, args)
    dim txt as c
    
    
    txt = "alert('" + "count <> 0 works!!" + "');"
    aa = e.rtc.A_AjaxResponses
    aa[].text = txt
    
    
    cn.CommitTransaction()
    
    end if
     	
    cn.Close()
    the select query in the above code works fine..........also the alert box pops up nicely but my table is not getting updated
    i used a sql profiler and according to it update query is not getting fired...
    the query is fine but i dint know why it wont work
    if anyone can help?
    Do reply!

    Comment


    • #3
      Re: update Query not working?

      Originally posted by prashantvarma View Post
      sqlCommand = <<%txt%
      UPDATE imOperationalMIS SET imOperationalMIS.nUnitIDFK = imCustomer.nUnitIDFK FROM imOperationalMIS INNER JOIN
      imCustomer ON imOperationalMIS.nCustomerIDFK = imCustomer.nCustomerID where imOperationalMIS.nOperationalMISID = :ID
      %txt%
      I think you're missing a select in your update clause. I also added an alias to keep from getting a circular reference error.

      Code:
      sqlCommand = <<%txt% 
      UPDATE imOperationalMIS SET imOperationalMIS.nUnitIDFK = (Select imCustomer.nUnitIDFK FROM imOperationalMIS IMO INNER JOIN
      imCustomer ON IMO.nCustomerIDFK = imCustomer.nCustomerID where IMO.nOperationalMISID = :ID)
      where imOperationalMIS.nOperationalMISID = :ID
      Also, if I'm correctly understanding what your trying to do, you can shorten up your code and save a trip to server by using something like this:

      Code:
      Dim cn as sql::connection
      Dim sqlCommand as c
      DIM args as sql::arguments
      dim rs as SQL::ResultSet
      dim count as n
      dim flagResult as l 
      
      cn.open("::Name::Intranet")
      
      cn.PortableSQLEnabled = .t.
      
      sqlCommand = <<%longstring%
      select count(imCustomer.nUnitIDFK) as Count from imCustomer imCustomer 
      INNER JOIN imOperationalMIS
      ON imCustomer.nCustomerID = imOperationalMIS.nCustomerIDFK
      where imOperationalMIS.nOperationalMISID = :ID
      %longstring%
      
      args.add("ID", convert_type(e.OldDataSubmitted.nOperationalMISID,"N"))
      
      cn.Execute(sqlCommand, args)
      'you should add error trapping here
      rs = cn.ResultSet
      
      if rs.nextrow() then 'will only return true if the result set has a row in it. 
      'if the row does exist, then we can just use the value in the column(s) we need to do the update.
      'Since :ID is already defined as an argument above, we'll just reuse it.
      sqlCommand = "UPDATE imOperationalMIS SET imOperationalMIS.nUnitIDFK ="+ rs.data("nUnitIDFk") +"where nOperationalMISID = :ID ;"	
      cn.BeginTransaction()
      cn.Execute(sqlCommand)
      'you should add error trapping here.
      cn.CommitTransaction()
      end if
      
      cn.FreeResult() 'good idea to get in the habit of using this 	
      cn.Close()
      
      txt = "alert('" + "count <> 0 works!!" + "');"
      aa = e.rtc.A_AjaxResponses
      aa[].text = txt
      Jim Coltz
      Alpha Custom Database Solutions, LLC
      A5CustomSolutions.com
      jimcoltz@a5customsolutions.com

      Comment


      • #4
        Re: update Query not working?

        Hi thanks for the reply....but it is still not picking up the update query....what i am done now is that i have enclosed my update query(the same Query used earliar) in a stored procedure and called the stored procedure int the after update event and it works fine.....but still i would like to know why it was not picking my update query.... please do reply...
        thanks

        Comment


        • #5
          Re: Debugging Query?

          Just put debug(1) at the begin of your Xbasic code

          Comment


          • #6
            Re: Debugging Query?

            Originally posted by tekri View Post
            Just put debug(1) at the begin of your Xbasic code
            And run the component in the Working Preview tab
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.

            Comment

            Working...
            X