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

<Fld>.inital_value_get

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

    <Fld>.inital_value_get

    I am want to know if the value in a field (�Price�)changes.
    I would like A5 to automatically store the value that �Price� had before a change was made into the field �old_price�.

    I have been able to fill the field �date_changed� with the date the field �price� changed.
    This was done in field rules, for the field �price�, in the events tab, field event, OnWroteField, with the following:

    tbl=table.current()
    tbl.date_changed=Date()

    I have found the method .intial_value_get() on page 271 of the Xbasic Reference Manual. What is the proper syntax or is there a better way?

    Thanks
    Tony

    #2
    RE: &lt;Fld&gt;.inital_value_get

    Tony

    Since you are already using field rules, that would one place you can handle this. You need to trap and save the original value before the change and then compare the values after saving a new value. This value can be saved in a shared variable.

    On the CanSaveRecord event for the table

    dim shared org_price as n
    tbl = table.current()

    org_price = tbl.price


    On the OnEnterRecord event

    dim shared org_price as n
    org_price = 0


    On the OnSaveRecord event
    '-------------- I use the OnSave rather than the CanSave so I only trap the value if the record was actually saved.

    dim shared org_price as n
    '---- org price = 0 only on a new entry
    if org_price = 0
    end
    end if

    tbl = table.current()
    '---- No action if price has not changed
    if tbl.price == org_price
    end
    end if
    '----- Ok, the price has changed
    tbl.change_begin()
    tbl.old_price = org_price
    tbl.date_changed = date()
    tbl.change_end()


    You can also use this method to update other tables when a field changes value rather that using posting. This gives the option to add a message box to allow the user to select if they want to change the related values or not.

    Jerry

    Comment


      #3
      RE: &lt;Fld&gt;.inital_value_get

      Jerry

      Would you mind taking a look at my code. I probably have some simple mistake, but for the life of me, I can't find it.

      CanSaveRecord

      dim shared org_price as N
      tbl=table.current()
      org_price=tbl.price

      OnEnterRecord

      dim shared org_price as n
      org_price=0

      OnSaveRecord

      dim shared org_price as n
      if org_price=0
      end
      end if
      tbl=table.current()
      if tbl.price==org_price
      end
      end if
      tbl.change_begin()
      tbl.old_price=org_price
      tbl.date_changed=date()
      tbl.change_end()


      When I change the price, the var org_price changes to equal price. I think this is causing the script to end and not letting the last of the OnSaveRecord to run.
      But then again, I don't have a clue. The date is not being inputed either.

      Thanks
      Tony

      Comment


        #4
        RE: &lt;Fld&gt;.inital_value_get

        Tony,

        Each code piece is placed on in the field rule record event listed above it. Since an example is easier to see, I have attached a single table example.

        Unzip the table. Do not mix with other work. Attach it to any database. Open the default browse. If you add a new record, nothing is added to to old price or date fields. If you change a value to the existing value, nothing happens. If you change the price, then the old price is saved and the date is entered.

        Open the field rules and goto events. You can see how it works. The code is cut and paste from my post with one exception. I added a round() to the values to make sure everything is checking to 2 decimals only.

        Jerry

        Comment


          #5
          RE: &lt;Fld&gt;.inital_value_get

          Jerry
          My problem was that I had the wrong event
          I was using the CanSaveRecord event
          and you used the CanChangeRecord event
          Works great now.
          Many Thanks
          Tony

          Comment

          Working...
          X