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


  • Filter
  • Time
  • Show
Clear All
new posts

  • Lookup

    I have imported a table from a POS system. The account_name in the POS system is different from the account_name in the primary database.

    So I have added a field to the primary people table called "POS_Account". Thinking that I can use lookup to read the value in the imported data (account_name) the read the value in the primary (pos_account), replacing "account_name" in the imported data with the correct value from the primary table. (Does that make sense?)

    PRIMARY.account_name = "Brodbeck, Alberta"
    POS.account_name = BRODBECKA

  • #2
    Re: Lookup


    You want to "correct" the account_name in the imported table? Has the POS_Account field been populated in the primary table?

    One way to change the account_name in the imported table would be to design a posting operation where the POS_Account is the linking field and use a lookup() to get the correct value to post. Another way would be to create a set with the imported table as the parent and the primary table as the child, linked on POS_Account, and design an update operation to update the account_name in the parent with the account_name from the child.

    The second option is usually easier, in my experience.
    There can be only one.


    • #3
      Re: Lookup

      I suppose you can do what you are proposing, but to answer your question "does this make sense," I think we need more information. For example, what use are going to make of the data in POS table? Is everything else in the two tables identical or is POS giving you additional data (fields) you need in addition to what is in your "Primary" table? When you import the POS table, does it contain just one record or are there many?

      I see Stan has beat me to this, but I still think we need more context.

      Raymond Lyons


      • #4
        Re: Lookup

        The PEOPLE table contains account information; credit terms, etc. The POS table contains transactions.

        I am a newbie here so bear with me please ...

        I want the "Account" field in the POS table to be the same "Account" shown in the PEOPLE table - so that I can summarize the data along with other account information. I have yet another transaction table - invoices, etc. - taken from Quickbooks. I want to join the pos transactions with that one.

        I think a "lookup" is what I want - but am struggling with what goes there.

        When I try this:

        It doesn't resolve to anything. I get "Invalid or imcomplete expression".


        • #5
          Re: Lookup

          I got it.

          lookupc("F", POS_ACCOUNT, "ACCOUNT_NAME","people","Pos_Account")


          • #6
            Re: Lookup

            This is wierd and I can't figure out how I did it. In the same table, the POS system uses the employee's intials as the userid. In the people table, this field ("POS_ID") is a 2nd field.

            In the import file, I see "jbw". When I import the transaction table, it gets transposed to "John Williams".

            This is done solely through a lookup on the lookup tab - and it is exactly what I want.

            So I have two tables:
            EMPLOYEE which has a person's name in it (as the primary key) and the initials are in a 2nd field
            POSTRANS which has the person's initials in it

            On the other hand, two tables:
            PEOPLE which has a person's name in it (as the primary key) and the CUST_ID which is a 2nd field.
            POSTRANS which has the CUST_ID in it.

            How come, when I do the import, the Employee name replaces the initials - but - the Customer name does not replace the "CUST_ID" value?


            • #7
              Re: Lookup

              Betty, the message board supports file uploads. Why not upload a zipped copy of the database (after purging or obscuring sensitive data)? If you supply a narrative set of directions for us to follow we can retrace your steps on our machines... and offer specific explanations to your general questions.


              • #8
                Re: Lookup

                I got it - again. And what it was was the linking field in the lookup was different.