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



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

Previous Values Lookup problem after Table/Field rename

  • Filter
  • Time
  • Show
Clear All
new posts

  • Previous Values Lookup problem after Table/Field rename

    I was wondering if anyone has seen this problem and has any tricks to try to correct it. I've experienced the same problem twice-- once, after renaming a table and field names, and the second after renaming a field only. In both cases, the fields now experiencing the problem contained a "Previous Values" Lookup field rule. Even after correcting any Field Rule settings related to the renaming and deleting/packing the table, if I reestablish a "Previous Values" Lookup, every time I open or edit the table I get a warning: "There are 2 warnings. Please view the trace window for details." It doesn't stop me from accessing the table in any way, entering data, or etc. but the warning messages reoccur.

    In the Trace Window, in the Error tab, the following continues to log:
    Warning [1]: Error(s) opening rules for field: BLDLOC_SHORTNAME
    Warning [2]: Error adding validation rule to database engine.

    The problem goes away if I define any other Lookup type for that field, or no lookup at all. Hmmm...while posting this and experimenting, I deleted the table currently with the problem and created a new one, with a different name and different field names, and I'm getting several sets of similar warning messages when I try to do anything with the table. As soon as I change the ONLY "Previous Values" lookup to a different type or none at all, the warnings all go away. Any idea where the corruption is?

  • #2
    Re: Previous Values Lookup problem after Table/Field rename

    The best way I have found to change field rules when I edit the table structure, is to remove the field rule, save and close the table, compact the table and then go and add the field rule back. It is the dictionary ghost you must get rid of.

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


    • #3
      Re: Previous Values Lookup problem after Table/Field rename

      Thanks for the reply. Ya, after the fact I suspected that would have been a much better approach. I was hoping to hear of an "exorcism" fix for the current situation. Because I haven't heard of anything and I don't like how it's been a little quirky since, I think I'll just rebuild the whole thing.


      • #4
        Re: Previous Values Lookup problem after Table/Field rename

        Warning #2 is a curious one, especially if you don't have any validation rules defined. I did have a dependency defined for the default value however. In my form, according to the tab order, that dependency was entered before the field that used it. But in testing I was using a default form and had forgotten to fill in the other field first - bingo same error. Once I filled in my fields in the proper order, no error was generated. You really have to consider how you expect the field order during data entry to work when defining your rules.

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