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

Form Filter Error

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

    Form Filter Error

    OK - I am new to Alpha and trying to learn. I am a long time Access user and have created advanced apps and such. Program VBA. I have gone through the 8 hrs of instructional videos that came with Alpha and did search the forum as to not be wasting anyones time.

    I have created a simple form with an embedded browse. I want to restrict the records to those that match a simple criteria (see attached). Form created in minutes, the browse automatically sync to the parent record... all is well. And yes, done in a fraction of the time this crude form would have taken in access.

    But, I am gettinga filter error. See attached. In the main form, I entered a filter expression built from the Alpha genie. Had to tweak the expression for true false, but it works. The form generates the error, but after you hit OK, it opens fine, filtered and all. If I go to form view from design view, no error. only when opening form from control panel. Other annoying part is when you go to properties of the form, sometimes the filter expression is gone. Unrelated to thread though.

    Sorry to write so much. If an Alpha believer could respond with any experience for this old Access guy, it would be great. Just trying to feel my way around and see if there are benefits of us switching. This form was a first start.

    Thanks

    Wayne

    #2
    Re: Form Filter Error

    I'll bet ysnactive is a logical field you've formatted to show on the form as True/False. If so you would need to test

    (Ysnactive <> .F.)

    or

    (Ysnactive = .T.)

    or merely

    Ysnactive

    Formatting doesn't change the underlying value (logical not character "False").
    There can be only one.

    Comment


      #3
      Re: Form Filter Error

      Thanks for the quick response Stan.

      You are correct, it is a logical field. In my SQL backend, it is a 0 or -1 value. In A5, its value is F or T.

      If I use a select statement

      (StrJobType <> "Service") .and. (Ysnactive <> "False")

      It returns the right value.

      I removed by formatting on the form (its back to F or T) and entered all three of your suggesions (Ysnactive <> .F.),etc.

      None of them actually filter the underlying values. Not sure if it is because of Link tables or something. It is apparent A5 does not like my use of filter text when it knows it is a logical field.

      Comment


        #4
        Re: Form Filter Error

        Not that familiar with the SQL backend. Are you using Alpha active link tables? If you do, what do you see in this field if you view the default browse? Can you screenshot the table's structure and a browse?
        There can be only one.

        Comment


          #5
          Re: Form Filter Error

          Attached are the screen shots.

          Yes, its is an A5 link table.

          Thanks for looking at this. I am sure this is an elementary question.

          In Access, I would not do a filter on the form. I would create a query and then base the forms data properties on the query. There is probably a way to do this in action scripting if I play with it.

          Comment


            #6
            Re: Form Filter Error

            Since I'm guessing.

            Try making the filter simply strjobtype <> "service". That should be ok. Then try only the logical test ysnactive <> .F., etc. Since you may be seeing Alpha's representation of the SQL backend, try ysnactive <> -1.
            There can be only one.

            Comment


              #7
              Re: Form Filter Error

              I tried ysnactive = 1 or ysnactive = T Both of these work.

              Basically, if you remove the .T. or .1. and let it look for text, the filter works great. Only issue is when you launch the form from the control panel, it errors out. If you launch from design view, no problems.

              I believe the issue is that A5 knows its a logical field and wants it the filter worded with the periods. Not sure if there is an expression that I could use to convert the logical to a string value in the expression.

              Thanks for your time... I think it is Give up time and move on.

              Comment


                #8
                Re: Form Filter Error

                Code:
                ? convert_type("T","L")
                = .T.
                ? convert_type("N","L")
                = .F.
                
                ? convert_type("0","L")
                = .F.
                ? convert_type("1","L")
                = .T.
                
                sqlbackfield = -1
                ? convert_type(sqlbackfield+1,"l")
                = .F.
                sqlbackfield = 0
                ? convert_type(sqlbackfield+1,"l")
                = .T.
                There can be only one.

                Comment

                Working...
                X