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

is this sql the right way to do an update

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

    is this sql the right way to do an update

    converting my app to SQL, i have lots of update scripts to switch from dbf to sql so i want to make sure before i go ahead and start the work that i am on the right track and have the most efficient way of doing this.

    All updates are run in the afterupdate event of a dialog or grid.

    this is the type of script i am changing
    Code:
    		'set progress values
    		dim tbl as p 
    		tbl = table.open("[PathAlias.ADB_Path]\progress.dbf")
    		'Find the record that has to be edited
    			query.filter = "caseref = " +quote(session.caseref)
    			query.order = ""
    			query.options = ""
    			qry = tbl.query_create()
    			nrecs = qry.records_get()
    			if nrecs > 0 then 
    			tbl.change_begin()
    				if totmths1 > 35 then
    					tbl.comp_res1 = "Completed"
    				else
    					tbl.comp_res1 = "Not Completed"
    				end if
    			end if
    			tbl.change_end(.t.)
    		qry.close()
    		tbl.close()
    this is what i have converted it to - this partuclar one needs an if, then, else but not all of them do
    Code:
    	dim cn as sql::Connection
    	flagresult = cn.open("::Name::MMLocal")
    	dim args as sql::Arguments
    	args.set("caseref",session.caseref)
    	args.set("COMP_RES1","Completed")
    	args.set("COMP_RES1NC","Not Completed")
    		if totmths1>35 then
    			dim sql_update as c 
    			sql_update = "UPDATE progress SET COMP_RES1 = :COMP_RES1 WHERE caseref = :caseref"
    			
    			dim flag as l 
    			flag = cn.Execute(sql_update,args)
    			cn.close()
    		else
    			dim sql_update as c 
    			sql_update = "UPDATE progress SET COMP_RES1 = :COMP_RES1NC WHERE caseref = :caseref"			
    			dim flag as l 
    			flag = cn.Execute(sql_update,args)
    			cn.close()		
    		end if
    do i need to keep opening and closing the connection if this is run from a grid/dialog?
    is there a way i can improve this for ease or efficiency?

    #2
    Re: is this sql the right way to do an update

    Hi Richard

    All looks good. Personally I try and open the connection at the last possible moment and close as soon as done. Probably would not make any noticeable difference in a short script.
    Glen Schild



    My Blog

    Comment


      #3
      Re: is this sql the right way to do an update

      hello
      just a little suggestion:
      you will need to check if the connection was successful or not at the connection level, and only proceed when connected.
      dim cn as sql::Connection
      flagresult = cn.open("::Name::MMLocal")
      if flagresult = .t.
      ......rest of your code
      else
      your_function_name = "alert('error in connecting to database!');"
      end if

      that will avoid any connection problems and to trap that.
      thanks for reading

      gandhi

      version 11 3381 - 4096
      mysql backend
      http://www.alphawebprogramming.blogspot.com
      [email protected]
      Skype:[email protected]
      1 914 924 5171

      Comment


        #4
        Re: is this sql the right way to do an update

        args.set("COMP_RES1","Completed")
        args.set("COMP_RES1NC","Not Completed")
        if totmths1>35 then
        dim sql_update as c
        sql_update = "UPDATE progress SET COMP_RES1 = :COMP_RES1 WHERE caseref = :caseref"

        dim flag as l
        flag = cn.Execute(sql_update,args)
        cn.close()
        else
        dim sql_update as c
        sql_update = "UPDATE progress SET COMP_RES1 = :COMP_RES1NC WHERE caseref = :caseref"
        dim flag as l
        flag = cn.Execute(sql_update,args)
        cn.close()
        end if
        also it may be possible to cut down some of the code
        comp_res1 = if(totmths > 35, "Completed", "Not Completed")
        then all you will need is one update statement.
        i did not test this yet, i will test this later today.
        let you know.
        thanks for reading

        gandhi

        version 11 3381 - 4096
        mysql backend
        http://www.alphawebprogramming.blogspot.com
        [email protected]
        Skype:[email protected]
        1 914 924 5171

        Comment


          #5
          Re: is this sql the right way to do an update

          thanks for the help, this seems to work

          args.add("COMP_RES1",iif(totmths1>35,"Completed","Not Completed"))

          Comment


            #6
            Re: is this sql the right way to do an update

            Actually, since this code fires when the data is updated - the SQL way to do this would be in an update trigger on the table.

            It will be a little faster, and it will fire even if you update the data from outside the grid.

            Comment

            Working...
            X