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

Case Convert Operation

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

  • Case Convert Operation

    I am attempting to save time with an existing Form by running a Script to convert the fields to Upper Case on the Table.
    The table is SQL and a mixture of Char, Numeric and Memo.
    The Form is a tabbed layout and the script should run OnSave.

    Building an Operation to create the Script code works on a simple Active Link Table properly.

    Building an Operation on a large table shows that the Fields are selected and moved into the correct box, but the code has a lot of bits missing when examined.

    I tried the long hand method to try and convert 2 fields and it killed AA completely.
    So, question. How to update all fields in an SQL Active Link Table to Upper Case - On Save?
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    There are 3 things you can do in any situation;
    Live with it, Change it or Walk away from it.

  • #2
    Re: Case Convert Operation

    I would think it would be simpler to loop through the fields on form and convert the values to uppercase in the cansave event.

    See how this works as the cansave event code.

    Code:
    lst = topparent.Child_Enum("r;f=field")
    for each chld in lst
    	typ = eval("typeof("+chld+".value)")
    	if typ = "C" .or. typ = "M"
    		eval(chld+".value") = upper(eval(chld+".value"))
    	end if
    next
    And there are form level field rules that might do just as well.
    Last edited by Stan Mathews; 09-21-2017, 08:39 AM.
    There can be only one.

    Comment


    • #3
      Re: Case Convert Operation

      You could use xbasic to(or manually) build an SQL update statement to update all the rows and fields and run that directly through an PHP admin or SQL control.

      Then use Stan's idea for new rows or use field options to upshift.
      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.
      "Make it as simple as possible, but not simpler."
      Albert Einstein

      http://www.iadn.com/images/media/iadn_member.png

      Comment


      • #4
        Re: Case Convert Operation

        Thank you gentlemen.
        Stan, I will try the code as soon as I get back into the application.
        My concern is that 160 or so fields being tested and updated through SQL might slow things down.
        The form level field rules will always work fine. It was a case of saving a bit of time, but it's probably better to do it at the field level on the Form as I would do normally.

        Al, we are looking at using SQL (Upper), depending on the data import. At the field level, we get rid of a load of back end work and it will be consistent.

        Just a bit shocked that the Operation let me down.
        See our Hybrid Option here;
        https://hybridapps.example-software.com/


        There are 3 things you can do in any situation;
        Live with it, Change it or Walk away from it.

        Comment


        • #5
          Re: Case Convert Operation

          Originally posted by Ted Giles View Post
          Building an Operation on a large table shows that the Fields are selected and moved into the correct box, but the code has a lot of bits missing when examined.
          I'm not sure what this means...
          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.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment


          • #6
            Re: Case Convert Operation

            I will post a pic tomorrow.
            But, select Operation, Change Case, Pick the Table, Select the fields, Move them over, Run.
            SQL works once.
            See our Hybrid Option here;
            https://hybridapps.example-software.com/


            There are 3 things you can do in any situation;
            Live with it, Change it or Walk away from it.

            Comment


            • #7
              Re: Case Convert Operation

              Originally posted by Ted Giles View Post
              I will post a pic tomorrow.
              But, select Operation, Change Case, Pick the Table, Select the fields, Move them over, Run.
              SQL works once.
              Are you using the operation genie?
              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.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment


              • #8
                Re: Case Convert Operation

                Yep!
                And tried editing the Xb
                See our Hybrid Option here;
                https://hybridapps.example-software.com/


                There are 3 things you can do in any situation;
                Live with it, Change it or Walk away from it.

                Comment


                • #9
                  Re: Case Convert Operation

                  This should process the entire table, not sure whether FILE_RW_EXCLUSIVE or .BATCH_BEGIN()/.BATCH_END() are appropriate with active link tables.

                  Code:
                  tbl = table.open("a")
                  flds = tbl.Field_Info_Dump("n,t")
                  cflds = ""
                  for each fldfnd in flds
                  	if word(fldfnd.value,2,",") = "C" .or.  word(fldfnd.value,2,",") = "M"
                  		cflds = cflds+word(fldfnd.value,1,",")+crlf()
                  	end if
                  next
                  to_update = line_count(cflds)
                  tbl.fetch_first()
                  while .not. tbl.fetch_eof()
                  	tbl.change_begin()
                  	for qx = 1 to to_update
                  		eval("tbl."+word(cflds,qx,crlf())) = upper(eval("tbl."+word(cflds,qx,crlf())))
                  	next
                  	tbl.change_end()
                  	tbl.fetch_next()
                  end while
                  tbl.close()
                  Or as an operation, self writing.

                  Code:
                  a_tbl = table.open("a")
                  flds = a_tbl.Field_Info_Dump("n,t")
                  cflds = ""
                  for each fldfnd in flds
                  	if word(fldfnd.value,2,",") = "C" .or.  word(fldfnd.value,2,",") = "M"
                  		cflds = cflds+word(fldfnd.value,1,",")+crlf()
                  	end if
                  next
                  to_update = line_count(cflds)
                  query.options = "I"
                  query.description = "Temporary Query"
                  i_indx = a_tbl.query_create("N")
                  update.fields = to_update
                  for qx = 1 to to_update
                  eval("update.field"+alltrim(str(qx))) = word(cflds,qx,crlf())
                  eval("update.expr"+alltrim(str(qx))) = "upper("+word(cflds,qx,crlf())+")"
                  next qx
                  a_tbl.update()
                  a_tbl.close()
                  Last edited by Stan Mathews; 09-21-2017, 04:03 PM.
                  There can be only one.

                  Comment


                  • #10
                    Re: Case Convert Operation

                    Looks good Stan. I will test tomorrow. Getting late here.
                    Many thanks.
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    There are 3 things you can do in any situation;
                    Live with it, Change it or Walk away from it.

                    Comment

                    Working...
                    X