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



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

Intersect Issues

  • Filter
  • Time
  • Show
Clear All
new posts

  • Intersect Issues


    I am new to Alpha Five and I having an issue with intersecting two tables.

    TABLE_ONE contains keywords such as: mouse, process, etc.

    TABLE_TWO contains a field, which the user entered concerning a problem.

    Specifically, I want to see if any one of the keywords from TABLE_ONE are located anywhere in the field of TABLE_TWO.

    Any thoughts?

  • #2
    Re: Intersect Issues

    Not sure where you want to "see" this. Download the attachment, unzip to a directory, add the tables to your database, try button on the form based on the problems table.
    There can be only one.


    • #3
      Re: Intersect Issues


      Thanks for the quick response. Reviewing my original posting, I realize that I had not been very clear in relating my problem. I apologize for not being clearer and allow me to restate my problem.

      I wanted to create an intersect table because of the amount of data I have to process.

      When I attempt to create an intersect table, I have the following:

      The Master is TABLE_ONE (the one with just the items) and I have the linking Key as FIELD_1.

      The Transaction table is TABLE_TWO and the Linking Key as FIELD_1
      (The one with the free form text)

      Both tables consist of Characters (C).

      I have the results going to a third DBF.

      Can someone tell me what the expression should be in the transaction table's linking Key to allow the searching of any of the text using TABLE_ONE's field_1 as the variable?

      Again, thank you for any assistance.


      • #4
        Re: Intersect Issues

        I believe a linking key has to be one value, not a searchable list. You could use an intermediary step which processed table_two creating a record for each of the words in the "problem field ".

        Problem field in one record contains "dead mouse". Result table contains two records, with all other fields the same, one with dead and one with mouse in the problem field.

        You should then be able to create an intersect with the result table based on the problem field.

        Have you considered not allowing the user to enter freeform text into the problem field. Give them a table lookup to the keywords from which they must select one. Your intersect then becomes unnecessary.
        There can be only one.