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
Devcon 2020 Goes Virtual! LEARN MORE >

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

* Primary Key Perplexity *

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    * Primary Key Perplexity *

    * PRIMARY KEY PERPLEXITY *
    ------------------------------
    Hi - I'm trialling v8 with a serious view to buy. Currently developing a Beta of a little dbase for my oil & gas client. I'm not an I-Techie but have used and designed dbases in a previous life (about 12 years ago).

    But I'm stuck on a basic issue and I'd be very grateful for some pointers from my local (UK) community...
    --000--
    So I'm trying to go the ascetic route in every table of this dbase: each table has as its primary key (well, that's what I'm calling it) a simple self-incrementing number, which is naturally unique, but also without contextual meaning. A bit like a serial number.

    OK, then I create a set which neatly links each table using these arbitrary but unique identifiers (keys); great. The problem comes when I enter data into the set using the default form: I obviously need to enter *numbers* to identify the particular records I want to retrieve - not what I'd like at all... Even if I set these key fields to be accessed via a pull-down object (in the form), I will naturally still only see numbers...

    If I could link the tables using these numerical PK's BUT get the pull-down object to show the *related* TEXT fields (descriptors) that would be first prize.

    I'm probably over-complicating my design, but if any fellow-user can make sense of my plight, I'd be very very grateful!

    PS: Does Alpha5 (v.*) have a strong (rigid) sense of primary key?

    Phil
    Tags: None
    #2
    Re: * Primary Key Perplexity !*

    Not sure why you posted this in the UK users forum so I'll butt in.

    I obviously need to enter *numbers* to identify the particular records I want to retrieve
    Not at all. You can have indices on any field and retrieve records quickly by making one ot these indices the currently controling index and retrieve records based on the contents of the indexed field.

    The user never need see the linking key field.

    Attached is a simple single table example of finding by indexed field.
    Last edited by Stan Mathews; 11-13-2007, 06:29 PM. Reason: simple example
    There can be only one.

    Comment

      #3
      Re: * Primary Key Perplexity !*

      Imagine a simple two table set. The parent (primary) table is linked to related records in the child table. The link in the set design is one to many, so many child table records may be linked to each separate parent table record. Ok?

      Your design must have unique primary key fields in the parent table. This primary key field would be used to define the link and a field corresponding to the primary key field must be present in each child table record. Call this second field a "foreign key". The foreign key field is the link that ties a record in the child table to the corresponding record in the parent table.

      The foreign key in the child table should never be set to autoincrement. The autoinc field values would break the link with the desired parent table record.

      Alpha Five is smart enough to make entry of the necessary foreign key field values automatic when new child table records are entered by the user. Just do the data entry through a set based form. Easy as pie. You should not try to display the foreign key field on your set based form. Nor should it be editable by the user.

      If you need to break a link by changing a foreign key field use a separate form based only on the child table.

      Alpha Five supports something else that you may find helpful. "Coded Lookups". check the help file for the details, but they wouldn't be needed in order to populate the link field values in new child table records, so long as the data entry is occurring through a form based on your set.

      Comment

        #4
        Re: * Primary Key Perplexity *

        Thanks to all of you for your responses... I have done further research based on your leads - and some great threads on this message board. So I have a little return offering - a static pic of the issue and how to set up a solution (with references)... Hope this helps others in the same predicament - many thanks again to the community.
        Regards
        Philip Oliver

        Comment

        Previous template Next
        Working...
        X