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

question - which way is best to populate fields

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

  • question - which way is best to populate fields

    I have documents with over a hundred fields that we are producing and which use, for instance State in these different way CA, Calif., California and California. There are thirty or so fields with these different possibilities.

    My question is which is the best way to populate multiple fields and would it be from a separate table or just use one field in the table working in?

    Also, how does one do it? Like Case(Field1 = AK , "Alaska", = AL , Alabama, etc.)

  • #2
    Re: question - which way is best to populate fields

    Are you asking how to translate "AK" to "Alaska" and the reverse should you want to use one or the other in a report, letter, etc?

    Don't know what that would have to do with populating fields.

    Build a translation table, for example for the states, and do a lookuip to it.

    Code:
    st = "Kentucky"
    ? LOOKUP("TRANS","STATE = "+quote(st),"s_abbrv")
    = "KY"
    sbrv = "FL"
    
    ? lookup("trans","S_abbrv = "+quote(sbrv),"state")
    = "FLORIDA        "
    You can have as many lookup tables as you want or the translations can all be in the same table (fields for each pair). Some records will not have values in the state and s_abbrv fields (for example) if there are more than 50 records in another translation pair.
    There can be only one.

    Comment


    • #3
      Re: question - which way is best to populate fields

      Hi Bruce,

      I know this is a little deeper than you might want to go for the moment, but the time will come!!!

      Have a look in the help file for CSTATES(). Not knowing what you are doing on your application, this could be of use to you.
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment


      • #4
        Re: question - which way is best to populate fields

        Actually this looks like exactly what I need.
        Thank you so very much. Will let you know.
        Bruce

        Comment


        • #5
          Re: question - which way is best to populate fields

          Question:

          I don't get how to use this as I am not sure how the symbols work.

          Could you write out the specific code to put in AL, AK, AR, AZ
          and then having that in one field, another field to be populated with Alabama, Alaska, Arkansas or Arizona? Somehow I am missing the actual how on this.

          It will have to be a click on this and paste it in, in both cases as this is something I will be using a lot and I am missing the specific how to's at this time.

          Thank you.

          Comment


          • #6
            Re: question - which way is best to populate fields

            Hi Bruce,

            I'm not sure what you are asking here.

            Do you want to select from a dropdown a State say "AL", in one field and have another field be filled with "Alaska"?
            Regards
            Keith Hubert
            Alpha Guild Member
            London.
            KHDB Management Systems
            Skype = keith.hubert


            For your day-to-day Needs, you Need an Alpha Database!

            Comment


            • #7
              Re: question - which way is best to populate fields

              I have field 1 ST for abbrev. AL, AK, AR, AZ

              I then have field 2 for State for Alabama, Alaska, Arkansas, Arizona which I want to populate automatically.

              And I have field 3 for State abbrev. Ala., Alaska, Ark., Ariz.

              So, when I fill in field 1 I want the others to fill in automatically with the correct designation. I also don't want any options to my states so it doesn't work well overseas which doesn't matter to me so I am forcing correct match. (Hope I spell everything correctly:)

              Comment


              • #8
                Re: question - which way is best to populate fields

                I have field 1 ST for abbrev. AL, AK, AR, AZ
                Where?

                I then have field 2 for State for Alabama, Alaska, Arkansas, Arizona which I want to populate automatically.
                Why?

                If you build the translation table as suggested you only need one field wherever the user enters the two character state code. If you want to display either the state name or the state abbreviation, you lookup the state code in the translation table and retrieve the desired value.

                There is no reason to store all three variations in each transaction record.
                There can be only one.

                Comment


                • #9
                  Re: question - which way is best to populate fields

                  Bruce,
                  Are you going to have tables used just for this purpose (lookup tables)---having all three fields filled in with the various data?? If so then Stan's script given would seem to be the easiest to do. You could do it all in code as well, but unnecessary really as it would as much work or more to put in all the various possibilities as it would be to create the lookup table.

                  Later--....Or Just listen to Stan!!
                  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


                  • #10
                    Re: question - which way is best to populate fields

                    So if I want Kentucky always spelled out, but want the user to enter KY, how would I go about doing this on a form?
                    I would create a table with two fields, I suppose: abbreviation and full_spelling.
                    What method would always replace KY with Kentucky?
                    (as an aside, I would probably also replace UK with "The greatest tradition in College Basketball", but I could figure out how to do this from the answer to my first question)
                    (and no, UK has nothing to do with the loosely united group of countries across the pond)
                    Jay
                    Jay Talbott
                    Lexington, KY

                    Comment


                    • #11
                      Re: question - which way is best to populate fields

                      Lookup the table and the field with KY in it, but fill with the field Kentucky in it. Easily done in the field rules.

                      Table to lookup = mystates and lfield and fillfield or whatever you wanna name them.
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment


                      • #12
                        Re: question - which way is best to populate fields

                        Dave,
                        Thanks for the quick reply, but the field where I want the effect to take place is a character 250 field.
                        So I want:
                        "Patient is from KY"
                        to automatically be converted to:
                        "Patient is from Kentucky"

                        How would I "fire" that change?
                        Jay
                        Jay Talbott
                        Lexington, KY

                        Comment


                        • #13
                          Re: question - which way is best to populate fields

                          One way would be a lot more typing(only once though), and I would have to think of something else to help. There is no reason that choosing KY in the look up could not fill in "patient is from Kentucky" if that was in the field used to fill your own.
                          Dave Mason
                          [email protected]
                          Skype is dave.mason46

                          Comment


                          • #14
                            Re: question - which way is best to populate fields

                            Dave,
                            I am not sure I understand your response. I cannot choose a lookup in the middle of a narrative.
                            If the narrative is going to change every time, that would not work. For example, the field might be used to describe the patient. It might say:
                            "The patient is from KY and he is tall and good looking"
                            That should translate to:
                            "The patient is from Kentucky and he is tall and good looking"

                            The next record might read:
                            "The patient is from FL and is extremely intelligent"
                            which should translate to:
                            "The patient is from Florida and is extremely intelligent"

                            See what I need?
                            Jay
                            Jay Talbott
                            Lexington, KY

                            Comment


                            • #15
                              Re: question - which way is best to populate fields

                              How about stritran() or evaluate_string()?
                              Peter
                              AlphaBase Solutions, LLC

                              [email protected]
                              https://www.alphabasesolutions.com


                              Comment

                              Working...
                              X