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

Problem with "set field value" action script

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

    #16
    Re: Problem with "set field value" action script

    Originally posted by Tbaker View Post
    I'm on 2299-3345

    Tom
    3345 - aex files
    2299 - dll/exe files (time for an update)
    Bill Griffin
    Parkell, Inc

    Comment


      #17
      Re: Problem with "set field value" action script

      Looks like there was an update at 10:00 am local time. I reported build wrong. My About dialog reports 2429 3346. Hmmm the beta notes page says the latest is 2431-3345 Obviously the code is in a state of flux.

      Back to the problem. Tom in your example (which was a copy of Keith's) the other button labeled 'Script' already had essentially your modification. But with a slight difference. The order in which the two fields get updated is reversed. In your example the Update button sems to work but the 'script' button still wants to change record focus before updating the date. If i give focus to the second record and push the 'script' button then the select column gets set to true in that second record but the date column gets set in the fifth(last record)
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #18
        Re: Problem with "set field value" action script

        Tim, I original posted the problem. The problem will show up only (best I can tell) in V10 development. V9 runtime works ok. Cant test it in V9 development because The V10 development has replaced bare V9.

        Problem will occur if you make the 2 separate actions into one or if you sequence them differently. The problem doesn't occur on the first record select in the browse, only when you select the second and additional records in the browse.

        Bob

        Comment


          #19
          Re: Problem with "set field value" action script

          Hi Bob,

          I can confirm that the example works fine in v9 development. I am seeing the problem (although slightly different) in v10 2429 3346.

          Would recommend you submit a bug report. After all that is the whole point of this beta phase. :)
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment


            #20
            Re: Problem with "set field value" action script

            Tim, bug has been sent... Thanks all for your input.

            Bob

            Comment


              #21
              Re: Problem with "set field value" action script

              Selwyn's reply to problem...

              i can repeat the problem using v9.


              the problem does not happen in v10 (which you don't have yet, and which uses a new version of the Browse)


              you can work around the problem in the mean time by changing your code to this:



              t = topparent:browse1.Table_Get()
              t.change_begin()
              t.SELECT = .t.
              t.EMAILDATE = date()
              t.change_end()
              topparent.Resynch()


              in v10 we are swiching to the new browse code that we have been working on

              Comment

              Working...
              X