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

Report setup problem

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

    Report setup problem

    I am having problems with fields in a body of a report. The report is based on a set. I am using two fields from a record ( db_1) that are company names specific to that record. I am trying to extract the address from my address database (db_2). db_1 is linked to db_2 via comp_id.
    The fields are set up in two columns.
    db_1 comp1_name db_1 comp2_name
    db_2 Address db_2 address

    For some reason, comp2_name is getting the same address as comp1_name.

    Any ideas would be appreciated.

    Larry

    #2
    RE: Report setup problem

    Larry,

    Please explain further.

    It looks to me as though your layout design is repeating the same named field on the second row two times... and you're unhappy with it? Wouldn't you have two differently named address fields, instead of two instances of the same field?

    -- tom

    Comment


      #3
      RE: Report setup problem

      Tom

      I am using the same address field on the second row twice as there is only one address field in db_2 for every record. My understanding is that the comp_id link field, extractes the correct address from the linked record in db_2. It is working for the first name field but why not for the second one?

      Larry

      Comment


        #4
        RE: Report setup problem

        Larry,

        what's the name of the field that has the second company address in it?

        Tell us more about your set structure. Is this a one to one link, or a one to many? Are you expecting address values from two separate child table records to appear on the same line in your report?

        -- tom

        Comment


          #5
          RE: Report setup problem

          Tom

          The address field is the same for all of the companies in the address db.This is a one to one link.

          Yes, I am putting the same field on the same line twice. Should I be doing something like columns?

          Larry

          Comment


            #6
            RE: Report setup problem

            Larry,

            Where is the address for company2 stored?

            I ask because your last posting really confuses me.

            If your parent table has two company fields, but it's linked one to one to a child table... and the child table only has one address field, it's no surprise that a second address is missing from the report. In this design I would have expected you to have two separate address fields in each child table record, each have a different name, like:

            comp1addr
            comp2addr

            Then you could put both fields on the same line in your report and arrange them so comp1addr is below comp1name
            and comp2addr is below comp2name.

            Does this make sense?

            -- tom

            Comment

            Working...
            X