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

Calculated field problems

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

    Calculated field problems

    I have a table with calculated fields called Worked, Not Worked and Overtime. Via Lookup I populate the Available field which is the standard contracted hours for the Employee.

    In the field rules Worked adds the daily hours worked by an employee and compares this with Available.

    The expression for Not Worked is IF((AVAIL>WORKED),(AVAIL-WORKED),0)

    I have a similar calculation for Overtime.

    I've been using this for about 2years on a form and until last week the Not Worked and Overtime changed as you entered the daily hours( which updated the calculated field Worked).
    Now Not worked and Overtime either don't calcualate properly until I save the record. I'm using field rules to calcalate on a calculation but this worked before.All fields are Numeric with 2 decimal places. I've run compact but can't think why this has suddenly stopped working.

    Any advice would be appreciated.

    #2
    RE: Calculated field problems

    Wondered if anyone could help with this problem

    Comment


      #3
      RE: Calculated field problems

      try restoring the ddm,ddd,sem,set and sex extensions from a backup prior to the problem occurring. Sounds like something corrupted and compacting may not help

      Comment


        #4
        RE: Calculated field problems

        Many thanks Robert. I did as you said and alls well again. Only problem is that i now have to redesign the forms that I've lost. I'm a bit worried that this has happened. Is this a common problem with Alpha5? I'm still developing some applications and am continuously changing my forms.

        Comment


          #5
          RE: Calculated field problems

          It's not a common problem, but it happens. Have a crash corrupt a memo field and don't find out about it for a few weeks and see how much fun you have if you haven't archived safeties.

          If the app is being used by anyone it's a good idea to make a safety at least daily and burn it to CD for off-site storage (a lot of people don't really worry about disaster recovery anymore - until it's too late).

          Crashes are inevitable. Storms knock out power, buildings burn down, someone accidentally brings in a virus after copying a screen saver off the web, you knock a Diet Coke over and it runs down into the server (well, actually, it was a private system at home that I was developing on - ended up buying some extansion cables and moved my systems away from the desk). During a database compact something happens to crash and you fry a table or data (I always start with a temp winzip before I do anything at night). During maintenance you accidentally empty and pack the wrong table . . . (I haven't yet but I'm waiting for it to happen). An append or post operation freezes up and you either have to restore a safety or work all night trying to figure how to fix the affected tables.

          As you work on developing stuff, it's a good idea to at least winzip and copy it to another directory. I don't know how many times I was working on something just to find out 5 or 6 major revisions later that I either needed to re-add something I'd removed, or fried something during testing and not had a problem surface for a dozen safeties. It also provides a means to archive your development in the event that a copyright issue surfaces later and you have to prove you're the originator.

          Comment

          Working...
          X