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

XBasic code indirection: setting field values

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

    XBasic code indirection: setting field values

    Hi folks,

    I was looking at the 'Code Indirection' example in the manual and rather than setting variables to the values in fields, I was trying to go the other way round.

    My script works if I name each variable-field pair explicitly e.g.
    t.Company = cCompany
    t.StartDate = dStartDate etc
    ...but if I try to refer to them indirectly as in the manual example, I get an assortment of errors (var mismatch etc) depending on what code I try. I have searched and searched for an example but cannot find one. I know I should teach myself how to use the debugger, and I will, but in the meantime, any help would be greatly appreciated.

    I will be happy to post my code, but it might be easier just to work from a slightly modified version of the example in the book which for your convenience is below. Note also that I am trying to do this for a series of records, not just one as in the book, hence the need to amend the example code slightly.

    Thanks for your time.
    MS


    CODE INDIRECTION EXAMPLE FROM THE MANUAL
    'Next line removed as my script is not a function
    'function xlookup as L(tablename as C, rec as N)
    'Next line added as example did not specify the table
    tablename = Table.actual_filename_get("cleaner upper")
    t = table.open(tablename)
    t.index_primary_put()
    'Next line changed to point to 1st rec
    t.fetch_first()
    num_fields = t.fields_get()
    'Next two lines added to handle multiple recs
    for rec = 1 to 20
    t.change.begin()
    for I = 1 to num_fields
    f = t.field_get(I)
    evaluate_template("dim global " + f.name_get() + " as " + f.type_get())

    eval(f.name_get()) = f.value_get()
    next I
    'Next two lines added line to close the multiple recs 'for' loop
    t.change.end(.t.)
    next rec
    t.close()
    end function


    #2
    RE: XBasic code indirection: setting field values

    MS,

    Not clear on what your goal is. i.e. don't know what you mean by 'the other way round'.

    If you have values stored in variables and you want to assign them to fields in your table you can do it directly, without any indirection being necessary.

    Assigning to fields in new records would use the routines described for tbl.enter_begin().

    Assigning to fields in existing records would include script commands to navigate to the desired records, one at a time, and then tbl.change_begin().

    If you want to update the same fields in a range of records in your table, using values stored in variables, i suggest you define an update operation.

    BTW, local custom is for real names to be used instead of handles or initials. You might want to re-register in the forum.

    -- tom

    Comment


      #3
      RE: XBasic code indirection: setting field values

      if you are trying to set fields to variables, then your code should be

      eval("t."+f.name_get()) = something
      or more simply
      f.value_put(something) -- the eval() function is not needed.

      you have written
      eval(f.name_get()) = f.value_get()
      which should set variables to the values in fields. notice your code repeatedly resets the same variables to new values as it scrolls through the records. you don't need the change_begin() and change_end() in your script since you're not actually changing anything in the table.

      Comment


        #4
        RE: XBasic code indirection: setting field values

        BTW, local custom is for real names to be used instead of handles or initials. You might want to re-register in the forum.

        There is no need to re-register to change your name that is displayed. Simply click the "Modify Your Preferences" link that is on the bottom of every page and update your name.

        -Lenny

        Lenny Forziati
        Vice President, Internet Products and Technical Services
        Alpha Software Corporation

        Comment


          #5
          RE: XBasic code indirection: setting field values

          Gentlemen,

          thank you for your responses.

          Tom, I will set up a 'real-name' account shortly but will continue as is here for continuity on this thread. Apologies for that legacy from when I first started looking at Alpha and didn't know them from Spam Inc.

          Peter, the line you suggest of...
          eval("t."+f.name_get()) = something
          ...was one of the three I had narrowed it down to. Thank you for providing certainty.

          Everything works beautifully now. That said, I do have one very small question:

          The .pdf and .chm help files will not let me search for "var->", so...
          If we have a variable called, say, firstname, what, if any, is the difference between...
          var->(firstname)
          ...and....
          eval(firstname)

          Thanks again.
          'MS'

          Comment

          Working...
          X