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

Error loading form after creating calc field

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

    Error loading form after creating calc field

    I created a new calculated field in a table (Consultants.dbf)
    The calculation is:
    "CDN-" + PADL(ALLTRIM(STR(CONSULTNUM)),LEN(STR(CONSULTNUM))-4, "0")

    This works ok when I enter a new record using the default browse.
    BUT
    I added the new calculated field to an old form (a very complex form... so I'm not anxious to redevelop it if i don't have to)...
    When I open this form I get a message saying that there have been 4 errors. The Trace window errors tab lists the fllowing:

    Warning [1]: Error(s) opening rules for field: PRIMEKEY
    Warning [2]: Error adding calculated rule to database engine.
    Warning [3]: Error(s) opening rules for field: PRIMEKEY
    Warning [4]: Error adding calculated rule to database engine.

    If I continue past the error mesage the form works ok.
    I tried compacting the workspace... didn't work.

    Is there a way to get rid of this message?

    #2
    Re: Error loading form after creating calc field

    In the PADL function, are you trying to remove the last 4 digits from CONSULTNUM in the LEN() function? Or change the length of the string from say 10 to 6?

    When I want to write a new calc field rule, i use the update genie to help write it.
    Last edited by MoGrace; 10-02-2014, 12:34 PM.
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #3
      Re: Error loading form after creating calc field

      Robin...Thanks for reply...
      The calc is working fine...
      "CDN-" + PADL(ALLTRIM(STR(CONSULTNUM)),LEN(STR(CONSULTNUM))-4, "0")
      It takes the Consultnum N9,0 field and converts it to a string... then trims extra spaces... then it determines how many chrs the str contain, subtracts 4 (because there are 4 chrs in "CDN-") and pads the string with 0's on the left side of the string... finally, it concatenates this string with the "CDN-" string. This results in a 10 chr string: CDN-000001 CDN-001277 CDN-987765 etc etc
      This function seems to be working fine... when I enter new records in the default browse it populates the field correctly.
      The puzzling observation is that when I placed this field on an old form it gave the error msgs that I listed in my original post.
      When I placed the field on a new form it worked ok!
      So...
      Since I had run into similar 'destruction' of old forms (the form I was working with was originally designed in A5V4)... I created a new form and copied fields, one by one, until it failed...
      In this case it failed on a seemingly unrelated field... a calculated field that employed a function... the mystery is that the function did not use the new calculated field in any term in the calculation... and it had been working for many years. It still does work... but not on any form that contains the new calculated field....
      So...
      I now have a new form that contains the new calculated field. It is working fine... but I had to delete the 'unrelated' {years old} field from the form. (If I put this field on a separate form it works fine). Fortunately the information provided by the old field was not used much so no one has missed it.
      Very strange... but... its now fixed (sort of).

      Comment

      Working...
      X