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

Need Help With Structure of Database

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

  • Need Help With Structure of Database

    I am creating a database (actually, restructuring a pre-existing one from Alpha 4) that holds contacts for fundraising purposes. Obviously, in the old database, information like the name, addresses, and contact numbers are stored. Right now there are two sets of fields for addresses and contact numbers for each record.

    I was thinking that I should take the address fields (primary and secondary address) and make them into a child table with each address as a record (rather than a bunch of fields) so I can accommodate more than two addresses and make it more efficient in general. I am also planning to add a field in the address child table that would denote whether the address is primary, secondary, etc., and perhaps another field that would say the kind of address (e.g. home, work, etc.). The parent table would have, among other fields, their name and their firm/company.

    A major function of the database is to print out labels and/or letters to the contacts in the database. I would want the letter or label to only print out the address record that is marked "Primary." But how would I get the firm name (since it is in the parent table) to be included in the address, if the primary address is the firm address? How would I get the firm name to not show up if the primary address is the home address? And how would I show the mailing address (whether it is the firm address or home address) to be properly displayed in a form. What's the best way to do all this?

    Any help would be very much appreciated.

  • #2
    RE: Need Help With Structure of Database

    "I would want the letter or label to only print out the address record that is marked "Primary."" - Are you sure? Would you never want to make a mailing to home addresses of persons whose primary address was work related? You might want to filter on all work addresses, all home addresses, certain zip codes.......

    "But how would I get the firm name (since it is in the parent table) to be included in the address, if the primary address is the firm address?" - I would put the firm name in the firm (work) address for use only if that address was used. But more to your point, if you can't get the firm name from the parent table, how will you get the name? I hope you plan to link the tables by some id number rather than by name. Just design the label based on the set rather than the child table.

    "How would I get the firm name to not show up if the primary address is the home address?" - Won't happen if it's attached to the child work address and not in the parent.

    "And how would I show the mailing address (whether it is the firm address or home address) to be properly displayed in a form." - Don't understand the question unless you're looking for expression help like

    total_name defined as trim(first_name) + " " + trim(mid_init) + " " + trim(last_name)

    st_address defined as trim(str_number) + " " + trim(str_name

    cty_st_zip defined as trim(city) + ", " + trim(state) + " " + trim(zip)

    assuming fields named as indicated, or your variations thereof substituted.

    There can be only one.

    Comment


    • #3
      RE: Need Help With Structure of Database

      Herbert

      Consider using a conditional object on the label that is based on where it is the home address or not. Then you can have one object have the firm name (if it's not the home address) and the other object not have the firm name.

      Have your record selection of the set that has the parent and child select only the child record that is the primary address.

      Should work really well.
      Al Buchholz
      Bookwood Systems, LTD
      Weekly QReportBuilder Webinars Thursday 1 pm CST

      Occam's Razor - KISS
      Normalize till it hurts - De-normalize till it works.
      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
      When we triage a problem it is much easier to read sample systems than to read a mind.

      Comment


      • #4
        RE: Need Help With Structure of Database

        Thanks for replying and in such a detailed manner. Let me answer some of your points and clarify my questions.

        You're right, there may be a time when I only want work addresses or only home addresses. But mostly, people just want there stuff (from us, at least) sent to one address, which we call primary. Usually it would be the firm address.

        The tables are indeed linked by an id number; that's not the problem. I was thinking that if I had a label template with a filter that it would only print out records marked "Primary" in the address type field, it would print out the address information but the firm name (if the primary address is the work address) would not be included in the address (because it is in the primary table, and is not in a field in the address child table).

        I guess I would have to put expressions or, as the Al suggested, a conditional object, in the layout itself. What's the best way to do that you think? And, in the same manner, how would I show the mailing address in, for example, a subform on the main form (i.e. a form would show the name and firm name on top, and below would be a subform or embedded browse with addresses).

        Hope I made myself a little clearer. Thanks again.

        Comment


        • #5
          RE: Need Help With Structure of Database

          Thanks for the advice.

          Comment


          • #6
            RE: Need Help With Structure of Database

            Herbert:

            If you have listings (people) linked 1:N to addresses in a set I would consider printing labels from an inverted set in which addresses are linked 1:1 to listings. This makes it simple to
            -filter the addresses to print, and
            -access the header information which goes with an address.

            Organizing address book and contact applications in this fashion has served me well.

            Bill
            Bill Hanigsberg

            Comment


            • #7
              RE: Need Help With Structure of Database

              Old Bill probably has the best advice. You might also consider having a field in the parent table that designates which type of address is "primary" for each name, restricting entry to certain allowable types.

              Then you could build a (separate) one-to-one set linked on id + primary_addr_type (in the parent) to id + addr_type (in the child) and print your labels based on this set.
              There can be only one.

              Comment

              Working...
              X