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

Grid Link Control Delimma and Solution

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

    Grid Link Control Delimma and Solution

    Here is the situation I ran into that I thought I would share that may help someone.

    The design: I have a table that stores client information including Last_name. I have a grid with the fields Last_name and First_name that is set to display {Last_name}, {First_name} (via Free Form Layout) with the First_name field hidden. The grid is also ordered by Last_name. The Last_name field is a Link Control to populate a detail view for editing.

    The dilemma: For clients with the same Last_name the link from the grid to populate the detail view will always bring up the record related to the first occurrence of the Last_name based on recno() order. So if I have 5 Smiths in the database and John Smith was the first Smith entered into the database, all other Smith Links in the grid will populate the detail view with John Smith�s data. So the logic behind the Link Control seems to be to always retrieve the first occurrence of the Link value regardless of the recno() that should be associated with the link in the grid.

    Given that I would like the interface of my project to remain the way it is letting a client click on Last_name to populate the detail view but actually get their record and not John Smith�s .

    My Solution: (probably one of many)

    I had an ID field in the table set to auto increment and is therefore unique. I added this ID field in the grid as a Link Control. I made it the Link to the Detail View and specified that the Link Display be set to the Last_name field instead of ID. I then used the Free Form Layout to populate the grid for the ID field as {ID}, {First_name} while hiding Last_name and First-name fields. This effectively maintained the interface as it looked before and corrected the Link problem.

    This is probably how I should have done it to begin with and I am not proposing that anything is wrong with the Link Control. However, this does point out how easy it is to use the Link control improperly. If you are using the Link Control make sure it is only used with a unique field value otherwise you are probably not getting what you intended.

    Chuck

    #2
    Chuck,

    My experience with relational databases is that it almost always makes sense to use an ID (autoincremented, unique) for most tables in the database...It keeps the database referential integrity clean...

    I always use only those KEY id fields to link tables with each other. When other field values change then the links are still intact.

    An exception is for instance a country table with country descriptions. Here I use the ISO abbreviations as a primary key (US, NL, etc) . These key values are not likely to change in the future.

    regards, Ron

    Comment


      #3
      Thanks Ron - I agree and I also always include a unique key field in my tables which inevitably was used in this case. However, it is not clear that using the Link control in a grid component to its detailed view is similar to linking tables. After all, the link is defined based on only one table (at least in the case I presented). I have not used a Link to a detailed view in another table and am not sure you can. There are no cascading changes to multiple tables and thus no compromised record references. The link in this case simply, and for lack of a detailed description, functions as an HTML hyperlink to another grid view of the same table.

      My problem is that the control lets us choose the linking field regardless of if that field is key or unique. This led me to assume it contained some logic that allowed to to workout the correct record to refrence (like embeding recno() in the link). If the control is not going to use recno() automatically to refrence the link back to the table it should not let us chose fields that will result in errors.

      Chuck

      Comment

      Working...
      X