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

in MS SQL Server, is a foreign key necessary

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

  • in MS SQL Server, is a foreign key necessary

    Having been a dbf guy for the past 20 years, I am on thin ice in the world of enterprise databases.
    So my question is (at the risk of what Mark Twain said):
    Is a foreign key necessary in the tables where it may be appropriate?
    Doesn't the grid relationship and lookup criteria do what a foreign key does?
    Or am I missing something?
    Thanks.
    Jay


    Mark Twain: It's better to keep you mouth shut and have people wonder if you are stupid, than to open your mouth and remove all doubt.
    Jay Talbott
    Lexington, KY


  • #2
    Re: in MS SQL Server, is a foreign key necessary

    I'm not sure what you mean by "grid relationship and lookup criteria", but you don't have to denote anything as a foreign key, even when it's applicable.

    Comment


    • #3
      Re: in MS SQL Server, is a foreign key necessary

      Thanks, Chris.
      By "grid relationship and lookup criteria" I meant that you can force the user to select from a list which in effect would have the constraint of a foreign key.
      Jay
      Jay Talbott
      Lexington, KY

      Comment


      • #4
        Re: in MS SQL Server, is a foreign key necessary

        That makes sense.

        Comment


        • #5
          Re: in MS SQL Server, is a foreign key necessary

          I think it is necessary if you want to make sure of the database integrity at the database level.

          You're right, the grid relationship and lookup criteria do what a foreign key does but what happens when the database is connected to many applications, i don;t tink that the integrity of the database will be enforced in this case.

          Comment


          • #6
            Re: in MS SQL Server, is a foreign key necessary

            WAS
            Lookup Properties/Dynamic Filter
            should select/filter the Lookup Fields to match the parent.
            Setting Foreign Keys up in SQL is a bit tortuous - Error 150 etc - and I try to avoid them and handle matters in the Alpha side. But I'm still learning too.
            I suspect that you will ultimately be responsible for managing the integrity in any event.
            Ted Giles
            Example Consulting - UK
            .

            sigpichttp://ec12.example-software.com//
            See our site for Alpha Support, Conversion and Upgrade.

            Comment


            • #7
              Re: in MS SQL Server, is a foreign key necessary

              Yes that's how it is enforced using alpha5 ... I am sorry though maybe i wasn't specific; what i meant was in case the MS SQL database allows connections to other users/apps; lets say that another app built in .NET can connect to the same database that alpha5 uses, in that case if the foreign keys constraints are not enforced at the database level there is a chance that duplicate records be inserted from the .net interface.

              If you re-create a table that was dropped, it must have a definition that conforms to the foreign key constraints referencing it. It must have the right column names and types, and it must have indexes on the referenced keys. If these are not satisfied, MSSQL returns error 150 in the error message.

              I think it would be worth it to learn more about this: W3Schools offers great tutorials about sql foreign keys constraints

              I am still learning too more about WAS events and javascript ...

              Comment

              Working...
              X