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

Special Case Conversion

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

  • Special Case Conversion

    If you have field rules in place to transform a person's last name with the transform command of Low & Word, in other words make the name all lower case and then capitalize the first word you may have run into situations where that doesn't provide the answer you want all the time.
    For example, if the name is McDonald, using the fields rules listed above, the name will be converted to Mcdonald. The field rules do allow you, in the Transform, tab to edit an exceptions table to make provision for the proper capitalization. That does mean that the user has to get to the field rules to do that. That of course is not a good thing and also what do you do in a network situation so that all users can have the same exceptions file.

    I found a work around. The exceptions are stored in the computer's c drive in the Alpha Five shared folder and is called a_case.dbf (Thanks Stan).

    To resolve the issue:
    1. Copy (not move or delete) the a_case table from your shared folder on your c drive to the folder where your database is.
    2. Add the table to your database.
    3. Create a simple browse screen for users to update.
    4. Create a new function called case_convert() (listed below)
    5. Add a line to your autoexec script like this:
    result = case_convert()

    The case_convert() function will then copy unique entries to the users local c drive from the database. Then all users will have the same thing to share, they don't have to go to field rules and it will be automatically updated each time they open the database. You could do a button to manually update the the local c drive or add an event to the network a_case table to update the local machine when they a new entry.

    The function returns a true/false when it run so you can do some error trapping if you wanted.

    Here is the function:

    'Date Created: 26-Mar-2010 10:27:27 AM
    'Last Updated: 26-Mar-2010 10:38:45 AM
    'Created By : mike
    'Updated By : mike
    FUNCTION case_convert AS L ( )
    DIM Append as P

    a_tbl = table.open(a5.Get_Shared_Path() + chr(92) +"a_case")
    append.t_db = a5.Get_Path() + chr(92) + "a_case.dbf"
    ON ERROR GOTO ERROR26032010103440457


    append.m_key = "old"
    append.t_key = "old"
    append.m_filter = ""
    append.t_filter = ""
    append.type = "Unique, replace existing"
    append.m_count = 2
    append.m_case1 = "EITHER"
    append.m_field1 = "OLD"
    append.m_exp1 = "@A_CASE->OLD"
    append.m_case2 = "EITHER"
    append.m_field2 = "NEW"
    append.m_exp2 = "@A_CASE->NEW"
    append.t_count = 0

    a_tbl.append()


    GOTO CONTINUE26032010103440457
    ERROR26032010103440457:
    ON ERROR GOTO 0
    'ui_msg_box("Error","Error running Append Operation"+crlf()+error_text_get())
    case_convert = .f.
    END
    CONTINUE26032010103440457:
    a_tbl.close()
    case_convert = .t.


    END FUNCTION
    Mike Reed
    Phoenix, AZ

  • #2
    Re: Special Case Conversion

    Thanks Mike for this. In case you or others need to "roll your own", I believe Cal Locklin has a script/function in the Code Archive for this as well that takes into account much of this scenario of exceptions. :)
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


    • #3
      Re: Special Case Conversion

      Yes it is true Cal has a similar option in the Code Archive.
      This one is a little different in that it uses the built in Alpha Five exception data base and functionality.

      Thanks,
      mike
      Mike Reed
      Phoenix, AZ

      Comment


      • #4
        Re: Special Case Conversion

        For sure Mike.

        I realized what you presented was a different option---in fact it went into my help file alongside Cal's alternative! :) Never one to want to have to start something from scratch when headstarts like these gems exist!
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment

        Working...
        X