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

unique key - discussion

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

    #16
    Re: unique key - discussion

    Instead of a Delete option in your application for records you may consider only allow (certain users) to De-activate a certain record.
    F.i. By checking a checkbox or having a valid date range for each record in your tables.

    Drawback is that you will have to filter those out for normal requests / usage in dropdown, popup, etc.

    But it secures that any references stay intact.
    F.i. for historical reporting reasons.

    Over time you can decide to build a clean up routine, which (cascading) deletes non relevant de-activated records in your DB before a certain date.

    This gives a different meaning to the D in the CRUD acronym.
    Last edited by rleunis; 07-02-2009, 03:50 PM. Reason: syntax

    Comment


      #17
      Re: unique key - discussion

      What about these settings as a solution for using UUID keys? Would this not work when coding record creation? Any potential snags?

      Field Rules

      >Data Entry
      >>Required = Always Required
      >>Auto Advance after field filled = checked
      >>Default Mode = Simple Default Expression
      >>Default Value = API_UUIDCREATE()
      >>Set Default Value at start of data entry = checked

      >Validations
      >>Uniqueness test = Value of field must be unique

      Comment


        #18
        Re: unique key - discussion

        I do not use UUIDs as a visible field on forms, etc. I don't want users to need to deal with something that long. My UUIDs are used for internal linking, and if necessary I provide an additional id that is shorter and more user friendly. This shorter id may use autoincrement or some other incrementing mechanism.

        I would not use the uniqueness rule because that will automatically add an index with "unique values only". You will generally have an index on this field showing "all" values, so the extra index is a waste of resources.

        Since I do not show this field to the user, and it certainly is not a user data entry field, I don't use auto-advance and required.

        Bill.

        Comment


          #19
          Re: unique key - discussion

          Thanks for the tips! I really appreciate knowing about the index based on the uniqueness rule.

          Comment


            #20
            Re: unique key - discussion

            I've got a bunch of apps running on a bunch of computers. In the past ten years I have had two autoincrement failures - the first was in maybe 2000, with an Alpha autoincrement field. I immediately converted to roll-your-own keys. In maybe 2007/2008 I had a failure with one of those. I emailed Bill, pointing out the irony.

            Where I have multiple offices, I have a 3 digit office prefix which I add to a 9 digit number, like EDW000001239.

            In some cases, I also have a simple audit trail calculated field equal to the machinename/cdate/toseconds(time())/useid
            Last edited by martinwcole; 08-04-2009, 09:30 AM.
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment

            Working...
            X