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

Using Previous Field Rule

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

    Using Previous Field Rule

    Is the previous fields rule under lookups supposed to retain the value for a field from the previous record?

    I have unchecked the display drop box as I just want to carry forward a balance that is then added or subtracted from.

    I'm pretty sure I have set up the field rule correectly but for some reason nothing shows when I access the next record, the fields remain blank.

    Any help would be appreciated

    Regards
    Greg

    #2
    RE: Using Previous Field Rule

    The "previous" record used depends on the active index, which can change, so results can be inconsistent unless you can be sure you ALWAYS use the same index. And depending on the index there may not even BE a previous record...

    You might play with the lookup functions, as you can specify whether to take the closest, first or last match using a specified index or filter. This might be more consistent.

    Comment


      #3
      RE: Using Previous Field Rule

      You don't want to use the "previous" rule under lookups. Use the "previous" rule under default mode.

      The lookup version creats a lookup of all previous values entered. The default version fills in the value from the last record in the file.

      Bill.

      Comment


        #4
        RE: Using Previous Field Rule

        Themis,

        I think that you may have results if you go to field rules, data entry and select default mode and then 'Use previous value as default'

        Michael

        Comment


          #5
          RE: Using Previous Field Rule

          "I just want to carry forward a balance that is then added or subtracted from. "

          Some thoughts

          I trust you have checked out the capability of posting rules. I use them, but double check them on forms with a color formula that shows black on yellow if the current balance does not equal what it ought to. The calculated check formula I use is
          tranbill = tablesum("trans","Invno="+alltrim(str(Invno))+".AND.CNTRCT=.F.","Cost")
          with the color formula
          if(Billed{}.AND.(Round(Amt,2)Round(Calc->Tranbill,2)),"Black on yellow",if(Print,"Black on green","Black on White"))

          If the invoice has a billed date, and the Amt field value is the same as the tranbill it shows black on white. If the tranbill is different than the Amt field it shows black on yellow (stands out on a browse like a ...) and if I have flagged it to print it is black on green

          Calculated rules are updated every time the field or form is refreshed.
          Field rules only update when the record changes EXCEPT when you use posting rules (and they still get miscalculated on occaision, hence my color flags...

          Comment

          Working...
          X