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 EXIST.

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

    Using EXIST.

    I am trying to learn more about the EXIST function. I already have a work around for this but for some reason I think this can be done easier. I have a table called answers that I created an index called "Flags" the filtering criteria for this index is if (weight_flag=.t. .and. no_flag=.t.) From a form that uses "client" as main table and "answers" as child(one-many). I run a query on client filter out only those records that EXIST in "answers" using the current index. So my filter in the query looks like this: EXIST(SSN,"answers.dbf","Flags") SSN is the linking field but I kow that doesnt matter. SO this is what I expect to happen. I expect EXIST to find all the SSN in answers.dbf that fit the "Flags" index. But I get 0 records found. Am I confusing you yet???

    Help?
    Jamin

    #2
    RE: Using EXIST.

    that "if" in front of (weight_flag=.t. .and. no_flag=.t.) should not be ther.Typo

    Comment


      #3
      RE: Using EXIST.

      The way I understand "exist()" is that

      EXIST(SSN,"answers.dbf","Flags")

      would return true for all records where a

      SSN "exists, is found, whatever" as a value in the

      Flags index of the answers.dbf.

      You are probably getting 0 records because you are looking for a number in a logical field, if I understand your setup.

      You say you have a workaround. don't you just want to query on (answers->weight_flag=.t. .and. answers->no_flag=.t.)
      There can be only one.

      Comment


        #4
        RE: Using EXIST.

        Hi Stan

        I am querying the main.set which uses the client.dbf as parent and answers.dbf as child. weight_flag and no_flag are in answers.dbf in a one to amny link. I want to query the client records by finding EXISTing records in answers.dbf. SSN is a character field in both client and answers tables. So my way of thinking is that EXIST will apply the index filter which will bring up only records that weight_flag or no_flag are equal to .t.. And then the query will only show the clients who have records fitting the index named(Flags) in the EXIST.

        Comment


          #5
          RE: Using EXIST.

          Hey Jamin,

          Read the definition of the exist() function

          EXIST( KeyValue, TableFilename, IndexTagName)

          SSN is not a keyvalue to be found in your Flag index, which as I understand it is based on the T of F found in the weight_flag and no_flag fields.

          There was a post here the other day about querying the child table and only showing records in the parent table which had child records. Check it out.
          There can be only one.

          Comment


            #6
            RE: Using EXIST.

            Hey Stan.

            That was my post. So I wont be asking myself. I dont trust me. :) Thanks again. So you think because SSN is not in the filtering process than it is not a valid keyvalue???

            Comment


              #7
              RE: Using EXIST.

              Nothing to do with filtering.

              My understanding is:

              The exist function returns a true value if, looking at the table named in the function, it finds that the keyvalue given in the function "occurs" in the set of index keys of the index tag specified in the function.

              You have a character field SSN which I assume to be Social Security Number. Whatever it really is it contains character expressions, say 412684879. Exist will never find that 412684879 "exists" in the snswer table index as an index keyvalue for the flags index.

              Or i'm reall off base as to how yu have things set up. I've been wrong before.........
              There can be only one.

              Comment


                #8
                RE: Using EXIST.

                Hey Stan this is the script attached to the form.

                tbl = table.current()
                query.description = "Flagged"
                query.order = "SSN"
                query.filter = "exist(ssn,'flags.dbf','Flags')"
                query.options = "I"
                tbl.query_create()
                sys_send_keys("{F5}")

                I get 0. even thou there is 5

                Comment


                  #9
                  RE: Using EXIST.

                  PMFJI,

                  Jamin, I don't recognize the query.option() you're using. You might try omitting or changing it.

                  Next, you might try removing the filter from your flags index definition. Then add a few records to the parent table without adding any child records. Run your script to verify that the new records are filtered out (since there are no corresponding child records). Let us know how this turns out.

                  If it works, then add back the filter to your flags index definition and try again. If it does not work, this may mean that the exist() function cannot work with an index that, itself, incorporates a filter. Let's hope not.

                  -- tom

                  Comment

                  Working...
                  X