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

Unique Records Based on Multiple Fields

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

    Unique Records Based on Multiple Fields

    I would think that I could figure this one out, but it's not coming. I have a table that stores information about sub-contracting projects being done for contractors. The table includes a Contractor field (which is looked up from a Contractor table) and a Project Name field (which is entered for the first time in this table). On the data entry form, when the user is first entering a new project, I need them to be able to look up and fill in an existing Contractor, then fill in a Project Name. At some point before the record is saved, though, I need to make sure that the combination of the Contractor plus the Project Name is unique. If it is not, I need to not allow the save and make the user create a unique Contractor/Project Name. (I do have a calculated Contractor/Project Name field that combines them both, but I don't believe you can specify that a calculated field must be unique.) What am I missing? I can't figure out how to do this. Thanks for your suggestions in advance.
    Tags: None
    #2
    RE: Unique Records Based on Multiple Fields

    One way to do it is to define an index as CONTRACTOR+PROJECT, and then set that index as unique. If the user tries to enter one that exists, the program will return an error, indicating that the combination of the two fields has to be unique.

    Keep in mind that if one name is misspelled slightly, you could end up with a new record that YOU know to be a duplicate, but the program doesn't. If you restrict the data entry to lookups, that should help avoid the problem.

    Comment

      #3
      RE: Unique Records Based on Multiple Fields

      Another way:

      In field rules/validations for the projects field, choose "value of expression must be unique" (it's in there somewhere) and use "contractor+project" for the expression. This way you will be able to supply a custom error message to display in the event the user attempts to create a duplicate record.

      Bill
      Bill Hanigsberg

      Comment

        #4
        RE: Unique Records Based on Multiple Fields

        Kevin,
        I've written a complete construction job tracking package. If your interested in some ideas I've attached a few screen shots. Hub1 is shot of a summary project hub form. If you notice the drywall bar there is a red flag next to the job component because it is behind schedule. Every time you fetch through the jobs and find the one you want you press the "Compile Job" button. This completely compiles all project components that have been pre entered in another form called the "Project Compiler". Hub2 is a shot of the same form after pressing the green button on the left of the Exavation bar. Hub3 is a shot of the same form after pressing the grey button to the left of the Excavation bar. The numbers to the left in the blue bar are "total days to do job"/"days past"/"days left". These are automatically calculated from start, stop and todays dates. Each project can have up to 153 components. The sample forms here only show 6. The user can also assign a display order in the "Project Compiler" and the job components will be built in that order from the top down. Since the job is built fresh each time the "Compile Job" is pressed, the order can be changed as jobs are finished so they go to the bottom. If you would like any more screen shots of the "Project Compiler" form or any others just let me know. I'd be interested in seeing some screen shots of yours if you would like to share them.
        Jeff

        Comment

          #5
          RE: Unique Records Based on Multiple Fields

          Thanks for the feedback. I knew there must be solutions that I wasn't thinking of. Much appreciated.

          Comment

            #6
            RE: Unique Records Based on Multiple Fields

            Jeff,
            The screens look fantastic. I'm on my way out of town, so I don't have time to fully digest them now, but I'll take a deeper look when I return. Thanks.

            Comment

            Previous template Next
            Working...
            X