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

  • Peter.Greulich
    replied
    Re: question - which way is best to populate fields

    Originally posted by Jay Talbott View Post
    (and please come and get some of this cold weather. it belongs in New England, not Central Kentucky).
    The good news is, Wednesday evening it is going to be 5-degrees here. Tomorrow evening will be a toasty 10d, and tonight 19d, almost cozy.

    Leave a comment:


  • Jay Talbott
    replied
    Re: question - which way is best to populate fields

    Peter,
    That looks like it will do the trick.
    I can make the find_strings and the replacement_strings as global variables, create a function, and fire the function upon exiting the desired fields.
    Thanks so much. (and please come and get some of this cold weather. it belongs in New England, not Central Kentucky).
    Jay

    Leave a comment:


  • Peter.Greulich
    replied
    Re: question - which way is best to populate fields

    Jay, trigger it anyway you want:

    Find_Strings= <<%str%
    FL
    KY
    MA
    %str%

    Replacement_Strings= <<%str%
    Florida
    Kentucky
    Massachusetts
    %str%

    Input_String = "The patient is from KY and he is tall and good looking" + crlf() + \
    "The patient is from FL and is extremely intelligent"

    Output_String = stritran_multi(Input_String, Find_Strings, Replacement_Strings)

    trace.WriteLn(Output_String)


    ==> The patient is from Kentucky and he is tall and good looking
    The patient is from Florida and is extremely intelligent
    Last edited by Peter.Greulich; 01-21-2013, 04:20 PM.

    Leave a comment:


  • aschone
    replied
    Re: question - which way is best to populate fields

    Originally posted by Jay Talbott View Post
    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
    You are gonna have fun with transposing the state abbreviation with the state name. Take special note of Al's suggestion of using **[KY]**. By surrounding the replace value with control characters you will only replace values that are intended to be replaced.

    Take for instance a couple of examples.
    "John came into to say hi." - In this example we do not want to replace "hi" with Hawaii.

    I have another example where KY could be use in the a medical sense and not mean Kentucky.

    Leave a comment:


  • Al Buchholz
    replied
    Re: question - which way is best to populate fields

    Originally posted by Jay Talbott View Post
    Peter,
    I understand those functions, but I cannot figure out two things:
    When to make them fire, and how to make them "dynamic".
    I guess I could make them fire on the CanDepart of the field(s) that are relevant, but I cannot figure out how to make them dynamic (so that KY gets replaced with Kentucky, and FL gets replaced with Florida).
    Thanks,
    Jay
    Jay

    I would think you need a combination of str(i)trans and a lookup using KY to find Kentucky.

    How is the original string being created? Can you put in **[KY]** ?

    Leave a comment:


  • Jay Talbott
    replied
    Re: question - which way is best to populate fields

    Peter,
    I understand those functions, but I cannot figure out two things:
    When to make them fire, and how to make them "dynamic".
    I guess I could make them fire on the CanDepart of the field(s) that are relevant, but I cannot figure out how to make them dynamic (so that KY gets replaced with Kentucky, and FL gets replaced with Florida).
    Thanks,
    Jay

    Leave a comment:


  • Peter.Greulich
    replied
    Re: question - which way is best to populate fields

    How about stritran() or evaluate_string()?

    Leave a comment:


  • Jay Talbott
    replied
    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

    Leave a comment:


  • DaveM
    replied
    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.

    Leave a comment:


  • Jay Talbott
    replied
    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

    Leave a comment:


  • DaveM
    replied
    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.

    Leave a comment:


  • Jay Talbott
    replied
    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

    Leave a comment:


  • MikeC
    replied
    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!!

    Leave a comment:


  • Stan Mathews
    replied
    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.

    Leave a comment:


  • SmartMLMer
    replied
    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:)

    Leave a comment:

Working...
X