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

Using variable for field name in filter expression

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

    #16
    Re: Using variable for field name in filter expression

    I don't think you can use eval() in the context of the expression builder to evaluate the table field value. It seems to be looking for a variable. I tried a bunch of ways and could only get it to work with a table pointer. I made an example to play with if anyone wants.
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment


      #17
      Re: Using variable for field name in filter expression

      Hello All,

      Attached is a sample database. When you open the one and only form, there is a detailed description of what is happening and the desired result.

      I really appreciate you guys taking a look at this. It seems that what I want to do should be fairly straight forward...I just can't seem to get past this filter issue.

      Thanks for all your help.

      Louis

      Comment


        #18
        Re: Using variable for field name in filter expression

        Mike C,

        You're right, you need varC-> or varD-> etc for it to work properly.

        I'm still in the ver 5 world, so I use what I know.

        Tom

        Comment


          #19
          Re: Using variable for field name in filter expression

          Here ya go Louis....hope it does what you want.

          I changed the variables to global as it just did not seem to like it when I had them as shared!....at least while I was in the expression builder.

          Changed the filter in the list box xdialog.
          Also changed the table structure for one Logic field that was misnamed. (think it was Lotic instead of Logic).


          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


            #20
            Re: Using variable for field name in filter expression

            Mike C,

            That works perfectly, thank you! I will study your code so that hopefully, the next time a similar situation comes up, I will be better prepared.

            Tim, Tom and Mike Wilson,

            Thank you for taking the time to look at this challenge and offer your input. I have learned from each of you and your assistance is truly appreciated.

            Now, I'm off to add some date values into this filter as well.

            Kindest Regards,

            Louis

            Comment


              #21
              Re: Using variable for field name in filter expression

              Glad it worked....when studying the code, I had left some in that does nothing currently--part of my experimenting....In the OnChange events of the two fields that set the filter the only code needed is

              Code:
              dim global vFld as c
              
              vFld=case(topparent:Test_Field_A.value = "North" .and. topparent:Test_Field_B.value = "Up","Logic_Field_1", topparent:Test_Field_A.value = "North" .and. topparent:Test_Field_B.value = "Down", "Logic_Field_2",topparent:Test_Field_A.value = "South" .and. topparent:Test_Field_B.value = "Up","Logic_Field_3",topparent:Test_Field_A.value = "South" .and. topparent:Test_Field_B.value = "Down","Logic_Field_4" )
              what follows it can be deleted.
              Mike
              __________________________________________
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau
              __________________________________________



              Comment


                #22
                Re: Using variable for field name in filter expression

                Mike,

                When I first looked at your code, I wondered why you were opening the table but I assumed you had a good reason...and after pulling my hair out on this one, I wasn't about to screw with success.

                I have since, removed the unnecessary code and all is working well.

                Thank you again for sharing your expertise. I hope I can repay the favor some day.

                Kindest,

                Louis

                Comment

                Working...
                X