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

variable field names

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

  • variable field names

    Is it possible to address a field by a variable, as follows

    var->fldname="surname"
    mast.fldname=tran.fldname

    Or some similar code.

    Thanks for any help

  • #2
    RE: variable field names

    The answer is probably yes. Can you detail the context in which you need to do this: table, form, report?

    Bill
    Bill Hanigsberg

    Comment


    • #3
      RE: variable field names

      Hi Ron,

      Yes, it sounds like your are talking about redirection. In A5v4 you might have to use the eval() function to evaluate to the actual field instead of just having a string that contains the name of the field. Just having the name of the field in a character variable doesn't tell Alpha that you want to deal with the field itself, the name is just a character string contained in the variable. The eval() function will 'evaluate' the string to the result of the expression (even if it's just a string).

      Good luck,
      Jim

      Comment


      • #4
        RE: variable field names

        Here's a script that allows you to specify the name of a field, then specify it's value. In order to see one possible use, I also included code to change the current record (this script would be run from a button on a form).

        fname=ui_get_text("FIELD NAME","Enter field name")
        fval=ui_get_text("FIELD VALUE","Enter field value")
        tbl=table.current()
        fp=tbl.field_get(fname)
        tbl.change_begin()
        fp.value_put(fval)
        tbl.change_end(.T.)
        parentform.resynch()

        Keep in mind that this works for character fields. You would have to change fval to ui_get_number to deal with a numeric field, and ui_get_date for a date field.

        I hope this is what you were looking for.

        Comment


        • #5
          RE: variable field names

          Ron,

          See my Lotto v4.5 application in the Code section of this BBS. It does exactly that.

          Regards,
          Melvin

          Comment


          • #6
            RE: variable field names

            Thanks for all the replies.

            As usual a pointer in the the right direction (or redirection) in this case was all that was needed.

            I have now achieved my goal.

            William for your information, I have a large table 440+ field table that is installed in 50+ customer applications, the core fields are the same but there are a few variations on each site.

            I wanted to be able to automate the archiving of data but ran into various problems along the way, calculated fields etc.

            Now I have a function copy_table(source,dest,option) that will create a new table if option is .t., or append to an existing table if option is false. I can filter the source table as requried.

            The key to my problem was catching and ignoring errors when copying to calculated fields.

            Thanks again all

            Ron

            Comment

            Working...
            X