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

Trace Error

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

    Trace Error

    Hi All,

    File attached, anyone figure why this error is showing.

    Can any one have a look at the attached dbase containing a table 'weeks' See if get same result as mine.
    The table functions OK but I am curious as to why the error shows.

    Open the trace window then edit field rules and save the rules then observe the error is generated in the trace window.

    Michael

    #2
    RE: Trace Error

    Mike:

    Just got caught in a similar 'trap' myself -- coudn't see the forest for the trees.

    The problem is LUMONTH. Your field rule expressions treat it as a [b]date[b] field and it [b]character[b], 9 at that! Look at the structure and the upper right corner of the field rule wiz.

    Don't feel bad. I spent about an hour the other day on something no less obvious than this. It's what we do, I guess -- because we're 'Gifted'!

    Ken

    Comment


      #3
      RE: Trace Error

      Mike:

      See, I just did another one. Forgot to insert the front slash in the second html 'b' tag. Just wanted to bold 'date' and 'character'.

      Ken again

      Comment


        #4
        RE: Trace Error

        Whoops - disregard all of the above.

        I'm still trying..

        Ken

        Comment


          #5
          RE: Trace Error

          Ken,

          The calc did return character.

          I have since removed the calc, reset the lumonth field to user, saved, closed then re-entered the calc and reset as calculated and all is now well.

          The error message no longer appears.

          Michael

          Comment


            #6
            RE: Trace Error

            Mike:

            I just did the same thing!!!!!

            I removed the calc designation and noticed a default expression you must have tried sometime during development.
            The whole bag it set for simple default and your expression was in the window! Apparently even with db compacts it didn't clear when first changed from 'default' to 'calculated'. I don't know about you .. but that scares me.

            Confirm this, and get back. Open your posted zip and just change the LUMONTH rule to 'user-entered' then open the 'data entry' tab and scroll down and see that default expression.

            Scary eh? Alpha saved BOTH - thank heavens for the trace messages.

            Ken again

            Comment


              #7
              RE: Trace Error

              This was my own error, not a bug.

              Sometime in the far past the LUMONTH field was a lookup field and I had switched it to calculated without removing the lookup simple list values. The trace window was reporting this without affecting the operation of table.

              Michael

              Comment

              Working...
              X