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

Duplicated Field Lookup Records (Active Link Tables)

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

    Duplicated Field Lookup Records (Active Link Tables)

    Hi all,

    I am developing a small project and facing some problems during development.


    Background:

    At first I created the database in Alpha Five (.dbf file) and then exported all the tables to PostgreSQL. Then I link them back to Alpha Five with Active Link Tables. Before I use Active Link, everything works fine initially.



    Problem:
    The combo boxes, browses and reports that work before Active Link Tables created are now not showing the correct records.

    For instance, when scrolling up and down, duplicated records show in combo boxes (which are defined with lookup field, see attachment) and some of the records are not showing in report by displaying blank in each field.

    The lookup works fine in the particular single table but showing duplicated records in the set.

    And a message box "Maximum session open tables exceeded" always pop up and stop me from opening a table, set or form until I close and restart A5. But it will come back again after a few times I open and close the tables, sets or forms (see attachment)


    Questions:

    Any idea how to figure out the cause of this problem? And solution?


    Your help would be most appreciated.

    Thank you.

    #2
    Re: Duplicated Field Lookup Records (Active Link Tables)

    I have tried to update indexes of the set/tables and compact the database and it does speed up a bit while opening a form. After that, based on the advice from an expert I removed all the frames (which were 4 initially) in the form and it does enhance the speed of opening form a bit more and the performance is acceptable now. Does this mean that I cannot use frame anymore due to performance consideration?

    As per problem I mentioned above, I defined the lookup in table field rule where the table that is looked up will be updated frequently. This works well in native .dbf file but not with Active Link Tables.

    From the forum, I found that instead of using table field rule I should apply XBasic function sql_lookup() to lookup the list directly from PostgreSQL (if I am not mistaken) in order to get correct records. However, I cannot find any tutorial to show how to write it in correct way. The quick help from A5 show this:
    Code:
    sql_lookup(* conn, C table, C filter, C result_Expression[, * args])
    Anyone can help? I wish to populate a list of records from a table into the field of another table like the ordinary table lookup in field rule.

    Your help would be most appreciated. Thank you in advance.

    Comment


      #3
      Re: Duplicated Field Lookup Records (Active Link Tables)

      I've been digging deep into this forum for these two days and found no related solution or explanation to my problem.

      In the mean time, I try to search sql_lookup() in the help file but came out nothing.

      I downloaded the .pdf A5V9 help file but found that it is A5V8 help file as I can't find any related information about active link tables. It is "What's New in Version 8" instead of "What's New in Version 9" stated under "What's New" title.

      It might be lacking knowledge in myself that cause this problem but is there anyone could share your wisdom and experience to help me find the answer?

      Thank you. :)

      Comment


        #4
        Re: Duplicated Field Lookup Records (Active Link Tables)

        After a lot of tryout, I found that:

        Duplication of records happens only in the table which has lookup from other table that are both linked in the same set.
        For instance, table_1 has field_1 and is lookuped (defined in table field rules) from field_2 of table_2.

        When table_1 is linked with table_2 within one set and the linking field is field_1 -> field_2, duplication occur;

        when table_1 is linked with other tables other than table_2, everything works well.

        This can also explains why it only happens within a set of tables but not in a particular table.

        I don't know if this is a correct conclusion and I am yet to find the cause behind it, however, this is what I see now.

        Hopefully someone could correct me if I'm wrong somewhere.

        Thank you.

        Comment

        Working...
        X