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

Field Rules Don't Work

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

    Field Rules Don't Work

    Good Morning,

    So, I've got a large file in a dabase that has been working for years. All of a sudden, it lost its field rules and I cannot get them back in action.

    I've tried changing the rules - nothing
    I've tried deleting and recreating - nothing

    The base file is NAMES and the set, which incorporates a few other files, is NAMESSET. I've made the changes to NAMES as well as NAMESSET - nothing.

    I've finally put a very, very simple data entry default rule in that LASTNAME2 = LASTNAME1. It's a membership application and was working fine, as I said, for years. And, this is not the only field in the SET that has stopped paying attention to field rules.

    Anyone have any ideas ???

    Thanks,

    Lar

    #2
    Re: Field Rules Don't Work

    Sound like some sort of corruption.

    Select the table, Edit Field rules, Rules menu, Delete All Rules.
    Compact the database.
    Close and restart Alpha.
    Then try recreating the rules.
    There can be only one.

    Comment


      #3
      Re: Field Rules Don't Work

      I agree. Took your advice. Copied the file, edit rules, delete all rules, out and back in. Rebuilt some of the rules.

      Looks like it recognized the rule. However, I can now see the rule in the DBF as well as the SET. The application main screen is over the SET and it appears NOT to be following the rule. I deleted the SET and recreated but still same results.

      ????????

      Comment


        #4
        Re: Field Rules Don't Work

        Larry,
        The field rules go in the table, although you can add them by way of the set. Be careful creating rules in a set that may depend on a set connection because the rule may not work if you use the table alone.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


          #5
          Re: Field Rules Don't Work

          There are no set field rules. The set field rule editor is just a convenience to allow one to create table field rules for all of the tables in the set in one place.

          The application main screen is over the SET
          No idea what that means unless you are saying that you have a form built on the set which you are viewing.

          Time to attach a sample of the table for which the field rules are misbehaving?
          There can be only one.

          Comment


            #6
            Re: Field Rules Don't Work

            I do. The form is built on the SET. I can but it's a really big file.

            Here's an overview:
            * The DBF, membership file, has name fileds for member 1 and member 2 - basically husband and wife.
            * The field names are NAMF1 (first name for member 1), NAMM1 (middle name) and NAML1
            * The field names are NAMF2 (first name for member 2), NAMM2 (middle name) and NAML2

            The rules is defined in DATA ENTRY tab as:
            IF(NAML1<>" ".and.NAMF2<>" ",NAML1,NAML2)
            So, if member 1 has a last name and there is going to be a member 2 with entry of the first name, I want member 2's last name to defauly.

            Works in the DBF but not in the form, which is built over the SET.

            Any ideas ?

            Comment


              #7
              Re: Field Rules Don't Work

              So, making some progress. For anyone interested, here's what I know and what I've done - so far.

              When adding a new member to the file, a button on the form puts up a popup for the user to select a COUNTY. Once the county is selected, the app buils a member # from the "next" member number in that file.

              When I added a new member using the "button", did not work.
              Went to the raw file and tried to just enter a new record. Worked.
              Created a new form over the set and - it worked. However, I only hit new record to add a new member.
              Back to the first screen in original form - didn't work.
              Got to puttsing around with the button, commented out everything but the ENTER NEW RECORD and - did not work.
              Hmmm...
              Created a new button that only had ENTER NEW RECORD - worked.
              Adding support to the new button to select a county - worked.
              Added back the logic to increment the county control number - still worked.

              Can the logic behind a button have this effect on a field rule ?

              So now, will redesign the button and clean up the FIELD RULES to see what happens then.

              More later.

              lar

              Comment


                #8
                Re: Field Rules Don't Work

                the app buils a member # from the "next" member number in that file
                Data entry field rules fire when data entry is performed manually or when performed via xbasic using the .enter_record(), .change_record() and .delete_record() Methods.

                Not sure if that is how you accomplished your data entry.
                There can be only one.

                Comment


                  #9
                  Re: Field Rules Don't Work

                  Hi Lar,
                  In these days of political correctness, you can't even assume that husband + wife = same last name ! Maybe you should try a 'ship same' type checkbox that you can code to add the last name field if by some (rare) reason they are the same ;)
                  Robin

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

                  Comment


                    #10
                    Re: Field Rules Don't Work

                    I had this situation refently, with family groups, not just same surname stuff.
                    To get around it, I had to create a "group id" and add people that way.
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    Apologies to anyone I haven't managed to upset yet.
                    You are held in a queue and I will get to you soon.

                    Comment

                    Working...
                    X