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

Global rule change

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

    Global rule change

    Hi,

    Apologies for the fact that I should know this - I've searched this forum to no avail.

    I want to change every field in my application so that, when modifying forms, etc., the cursor goes to the end of unselected text. Obviously, I could spend a few hours doing it field by field, but how can I do this globally? I'm sure I've seen some way of doing it, unless I'm thinking of some other DBMS.

    Thanks if you can point me in the right direction.

    Martin.

    #2
    Do you want to change the table field rules for each field in each table to have the cursor position at end of "unselected text". (I'm confused by "when modifying forms, etc.")

    This snippet will do that for a named table.

    Code:
    tbl = table.open("tablename",FILE_RW_EXCLUSIVE)
    nFlds = tbl.fields_get()
    rul = tbl.rules_get()
    FOR i = 1 TO nFlds
    	fldname = tbl.field_get(i).name_get()
    	rul.change_begin()
    	evaluate_template("rul."+fldname+".cursor_pos = "+quote("End_Of_Unselected"))
    	rul.change_end(.t.)
    NEXT i
    tbl.close()
    It shouldn't be that difficult to wrap this in something that fed it all the tablenames in the database.
    There can be only one.

    Comment


      #3
      That's brilliant, Stan. Thank you. I'll do that next week. It would be a useful (and easy?) facility to build into a future version, Alpha?

      I won't risk it this evening because it's 7.45 pm here in England and although the sun is a long way from setting over the Avon Gorge and Downs (where I live and work) my wife has persuaded me to drink a couple of glasses of cab. sav. - (Australian, actually, although I know Kentucky has a long history of vinyards and wine-making but I've never seen any KY wine over here in the UK. Why not?)

      Thanks, Stan.
      PS I expect you know that you are only one letter away from being an English Knight -http://www.bbc.co.uk/stoke/local_heroes/sir_stan/index.shtml

      Comment


        #4
        If heard of that other guy from someone else, I think.

        Kentucky is known for bourbon more than wines but I do enjoy wine. I prefer the whites and blushes to the reds. Kentucky is also known for fast horses and beautiful women. (That might be beautiful horses and fast women, I can't keep it straight.)

        Enjoy your evening and the weekend.

        Here's the global version. It was pretty much a straightforward substitution into the documentation example for A5.table_enum().

        Code:
        table_name = :a5.table_enum("")
        IF table_name <> "" THEN
        	i = 1
        	'While the table_enum method returns nonblank names, get next name
        	WHILE table_name <> ""
        		:Statusbar.Set_Text("Changing cursor position field rules for: " + table_name)
        		tbl = table.open(table_name,FILE_RW_EXCLUSIVE)
        		nFlds = tbl.fields_get()
        		rul = tbl.rules_get()
        		FOR i = 1 TO nFlds
        			fldname = tbl.field_get(i).name_get()
        			rul.change_begin()
        			evaluate_template("rul."+fldname+".cursor_pos = "+quote("End_Of_Unselected"))
        			rul.change_end(.t.)
        		NEXT i
        		tbl.close()
        		table_name = :A5.table_enum(table_name)
        	END WHILE
        END IF
        :Statusbar.Set_Text("Done!!")
        Last edited by Stan Mathews; 06-02-2006, 03:15 PM.
        There can be only one.

        Comment


          #5
          ...and you, Stan. Watch out for those women and horses. They're more than a match for any man, living or dead. (That doesn't make sense, but I've had another glass...)

          Comment


            #6
            Stan,

            evaluate_template("rul."+fldname+".cursor_pos = "+quote("End_Of_Unselected"))
            Is this info in the help docs somewhere? I ask because there are a lot of field rules and I would imagine we can do this with other field rules as well?
            Cheryl
            #1 Designs By Pagecrazy
            http://pagecrazy.com/

            Comment


              #7
              Originally posted by Cheryl Lemire
              Stan,



              Is this info in the help docs somewhere? I ask because there are a lot of field rules and I would imagine we can do this with other field rules as well?
              I'll have to get back to you Monday.

              If I remember correctly, I used

              tbl =table.open("sometablename")
              fld = tbl.field_get(1)

              ? fld.rules_get()
              'rules were listed
              tbl.close()

              and thus got a list of rules and present values.

              I then changed the data entry for the first field to reflect "end of selected text"

              repeated the steps above and found that the rules value was

              "End_of_Selected"

              That way I knew the value that should be written to the rule to make the change.

              I think much the same would have to be done for all of the field rules possble settings to discover the allowable/pertinent strings to be written.
              There can be only one.

              Comment


                #8
                Thanks Stan. I will play around with it during the week and put it in my toolbox :)
                Cheryl
                #1 Designs By Pagecrazy
                http://pagecrazy.com/

                Comment


                  #9
                  Thanks again, Stan, that works perfectly. I'm surprised it's not possible in Alpha.

                  Comment

                  Working...
                  X