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

Lookup construction problems

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

    Lookup construction problems

    Hi there,

    Have a problem here that I'm struggling with.

    This has been working successfully for a while, becoming mode inconsistent with time.
    Changed name of Lookup table - maybe has something to do with it ?

    When accessing Field Rules in Table Acc.dbf Lookup fields

    AC_STMTRQF
    AC_TRMDCRF

    ..it keeps grumbling "No such Field"

    Any ideas ?

    Have included the db. (disregard mess "Error opening Startup form...")
    Attached Files
    Dave Mac

    It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

    #2
    Re: Lookup construction problems

    When I remove the default expression for those two fields the issue disappears.
    There can be only one.

    Comment


      #3
      Re: Lookup construction problems

      How you doing ?

      Well, I dug out all the defaults of these fields and buried them six foot under,
      so we are not likely to see them again. But i still got a problem.

      I am attaching a screen of my problem which I should have done in the first place.
      Attached Files
      Dave Mac

      It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

      Comment


        #4
        Re: Lookup construction problems

        Saw that here as well. Didn't happen after I removed the defaults and set to No Default.

        Testing further, when I close and reopen the database I see that warning again. Invesitgating further.
        There can be only one.

        Comment


          #5
          Re: Lookup construction problems

          Thanks Stan
          Dave Mac

          It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

          Comment


            #6
            Re: Lookup construction problems

            It could be an index problem. Try removing the field rules from that field, save and close. Then compact the table to clear the dictionaries and then reset your field rules.
            Robin

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

            Comment


              #7
              Re: Lookup construction problems

              Hi Robin,

              Thanks for the suggestion. Tried it on my db - but still the same.

              Interesting though, When i tried your suggestion on the subset db I sent with this thread, it did eventually work !!
              Not sure what the difference is ?

              I am attaching the working version. maybe you can pick up why the subset now works and the main db still not

              As we say in South Africa "Sterkte" from our dutch which translates to Strength but with a slightly different nuance.
              Attached Files
              Dave Mac

              It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

              Comment


                #8
                Re: Lookup construction problems

                Hi there,

                I eventually settled for Simple List rather than Lookup Table and it works ok.

                However, was still unhappy with the compromise. I eventually repositioned the problematic fields in the Table acc. I used the selfsame Lookp tables and got it to work. Was a little worried that Alpha5 would tolerate the repositioning but it seems ok.

                Just to advise anyone else out there who may have the selfsame trouble.

                Thanks to all of you for your assistance.
                Dave Mac

                It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

                Comment

                Working...
                X