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

List Control detail View Error mapping primary key fields

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

    List Control detail View Error mapping primary key fields

    I have a list control based on a mysql inner join of tables. I circle back to a table and link it a second time through another table with a FK relationship. So in the join I have the participant table and then when I use the participant table for a second time via a different linking table Alpha gives it a unique alias participant0. So I'm using participant, and participant0 in the query.

    The Query runs fine in the builder, all the tables and the fields are there. The common columns from the participant table are given unique names by Alpha: eg P_Id, and P_id_1.

    I proceed to create the detail view: I go to table properties and map the primary keys to the list query fields. (I think I did this correctly because I had no problem with this when I was not using the participant table twice). I then use fieldmap and map First, Last, from participant, and First_1, Last_1 from participantt0 to corresponding textbox controls I created for the detail view.

    However when I OK my way out of the builder I get an error dialog box. What am I missing? It seems like it won't allow me to use the table twice.

    There is an error in the Map primary key field(s) to list query field(s)' property for table 'participant0 (participant)'. Please go to the Detail Veiw tab and edit Table Properties.
    The primary key field(s) for this table are either not in the list query or have not been correctly mapped in the 'Map primary key field(s) to list query field(s)' property
    Help!
    Last edited by bob9145; 06-14-2015, 12:10 AM.

    #2
    Re: List Control detail View Error mapping primary key fields

    You can normally bind to the same field several times but only one can be set updatable.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


      #3
      Re: List Control detail View Error mapping primary key fields

      Thank you Peter,
      If I uncheck Allow update and check read only for the fields from customer0 within the detail view table properties the detail view displays the fields from the customer and customer0 as desired. Customer fields update when saved, & synchronized. Customer0 fields do not update as set.

      I don't understand why this limitation exists? Can someone give me more insight on this? Why couldn't the update statement be customized to make this work? Is this just a limitation of the builder?

      Comment


        #4
        Re: List Control detail View Error mapping primary key fields

        If you are setting a parent table and x number of child tables you must not include the related field in the child tables on the UX at all, they are managed by the UX when you set the relationships (they are assumed) up in Data binding Select Tables. If you do bind them SQL will see them twice and fail.
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment

        Working...
        X