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

split field

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

  • #16
    Re: split field

    Originally posted by MoGrace View Post
    Jim,
    Now you have me curious



    How did you get the genie to filter out these titles? And what will you do about the 'period' that most titles include?

    I think you know more than you are letting on!
    Robin,

    That code would have been generated by the "Break a Name into its parts" which did not work for Jim. What would (and apparently did) work was the "Break a Field into its parts". To deal with titles with periods, etc. would require, at the very least, a modified version of the code generated by "Break a Name into its parts". With complex names the expression required can get extremely complex, not something a genie can do on its own.

    Ray Lyons

    Comment


    • #17
      Re: split field

      Ray
      I used that expression but had to restore my database after it was done. It not only removed the blank in front of the first name but it removed all the blanks in the name.
      For example. Joseph Ray became JosephRay and Mary Anne Helen became MaryAnneHelen
      Jim Belanger

      Comment


      • #18
        Re: split field

        Robin
        In my case there were no titles and no periods so I wasn't really worried about those in what the genie wrote.
        Know more than I'm letting on? Well, I used to be pretty proficient as an amateur with Alpha but I haven't touched it since I retired 10 years ago. That's why I'm still using V9 and I've forgotten so much I find myself lost doing things I used to be able to do.

        You didn't ask for this but: I started with Alpha way back in the beginning; then upgraded up to V9 from V1. I never developed for anyone but myself. I had three businesses and used it in different formats for all three. But, Alpha is really designed for developers who progress along with upgrades, etc. Alpha is not friendly to users who simply want to continue using a program as they don't support older versions with any upgrades. I've contacted them because I was hoping to keep up with newer versions but at the price you have to pay as a developer; it's not economical when you no longer need to "develop" but simply to keep using. Oh, heck; you didn't ask for all this!!!!
        Jim Belanger

        Comment


        • #19
          Re: split field

          Hi Jim,
          Sounds like we are in the same boat with the desktop. It makes little sense to me to move to a yearly subscription just to keep going on a program I have already purchased.

          As for splitting your name into separate fields, the word() function ought to do it. If you are getting a leading blank for the first name field, you can modify the code the genie creates by wrapping it with ltrim().

          lastname = word(fullname, 1,",")
          firstname = ltrim(word(fullname,2,","))

          That should leave a last name like De Nova intact as well as a first name like Mary Jane.

          You might even try including the trailing space with the comma as the delimiter and leave off the ltrim() for the first name.

          lastname = word(fullname, 1,", ")
          Last edited by MoGrace; 07-02-2015, 12:23 PM.
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment


          • #20
            Re: split field

            Originally posted by Beltronics View Post
            Ray
            I used that expression but had to restore my database after it was done. It not only removed the blank in front of the first name but it removed all the blanks in the name.
            For example. Joseph Ray became JosephRay and Mary Anne Helen became MaryAnneHelen
            My bad--sorry. I was trying to limit you to nothing more than what the Genie would generate, which sometimes is the easiest way to do something, and sometimes it is not. What Robin has given you will solve your problem (I presume). So would a simple Ltrim() on the first name field the Genie produced with Break Field into its Parts.

            Or you could modify the first name expression the Genie produced for Breaking a field into parts by replacing the RED "1" in the code below withe a "2".

            Code:
            if(AT(",", FULLNAME, 1)>0,SUBSTR(FULLNAME, AT(",", FULLNAME, 1)[COLOR="#FF0000"][SIZE=5][B]+1[/B][/SIZE][/COLOR], (AT(",", FULLNAME, 2)-AT(",", FULLNAME, 1))-1),"")
            That is, with this:
            Code:
            if(AT(",", FULLNAME, 1)>0,SUBSTR(FULLNAME, AT(",", FULLNAME, 1)+2, (AT(",", FULLNAME, 2)-AT(",", FULLNAME, 1))-1),"")
            But my guess is that is just too confusing!

            Ray Lyons

            Comment


            • #21
              Re: split field

              Thanks to everyone. The Ltrim funtion worked perfectly. I chose not to combine the date since I deal with American and European dates all the time so having it split works just as well for me. I don't use dates in calculations in this dbase anyway.
              Jim Belanger

              Comment

              Working...
              X