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

set report problem

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

    set report problem

    Set for material inventory � `mtrl_set`
    Table: mtrl_in (primary) & mtrl_out (child)
    linked by mtrl_in_no & mtrl_out_no (one to many).

    Each inventory item `mtrl_in_no` has specific number and `mtrl_out_out` uses same no.
    Example: mtrl_in_no: 1a�`qty_in` - 100 pcs (one record)
    Mtrl_out_no: 1a-`qty_out` - 50 pcs / 10 pcs / 30 pcs (3 records)

    Report: on mtrl_set : report calculated field:
    ttl_qty_in: total(qty_in,grp->inventoryin)
    ttl_qty_out: total(qty_out,grp-nventoryout)
    balance: ttl_qty_in-ttl_qty_out
    result: ( 100-90) - balance =10
    this works fine

    problem: in case a new item added `SAME INVENTORY` in table: `mtrl_in`
    example: 2a � 300 pcs
    and it does NOT have even ONE qty_out record for 2a.
    total(qty_out,grp->inventoryout)
    evaluates to `0` (zero)
    it just ignores qty_out figures of 1a.
    and balance shows as: 400 (when it should show as : 310).

    If create one dummy record for 2a in mtrl_out with qty: 1 then the total of qty_out is generated correctly. (309 )
    (qty_in & qty_out are required fields in field rules)

    would appreciate if can point out what am I doing wrong. Have tried linking with inventory but the report generation goes into long calculations & about 450 pages are generates as there are over 2000 records in `mtrl_out` & over 50 inventory items but the problem is same while with link as made the report is instant & decent 80 pages

    Rgds,
    v.p


    #2
    RE: set report problem

    V.P.,

    In the typical one-to-many set there is only one record in the parent table which links to the related child table records. Your description suggests to me that perhaps you are storing more than one 'inventory_in' record for each item in your parent table. Instead of a one-to-many set, which your report is expecting, you are storing records as though the set had a many-to-many link. If this is what you are doing then that probably explains the behavior you are seeing.

    Consider rearranging your set design. I can think of two approaches:

    1) Use three tables. One, which will be the parent in your set, contains descriptive information about each inventory item, but no quantity information. It could be linked to an 'inventory_in' transaction table where you track additions to each inventory item, using the inventory item part number as the link field. A third table would be used for the 'inventory_out' transaction table, where you track the usage of each inventory item, again using the part number as the link field back to the parent table. One parent table, two child tables each linked one-to-many to the parent. No grandchild tables.

    2) Use two tables. One, which will be the parent in your set, contains descriptive information about each inventory item. Each item is given a unique inventory part number to distinguish it from the other items. A second table would be used to track both additions and usage of inventory items. It would be linked one-to-many to the parent table, using the part number field as the link. It would contain a quantity field, and a transaction_type field. The transaction_type field would be 'In' if the transaction was adding items to the inventory, and it would be 'Out' if the transaction was removing items from inventory.

    I think the second scenario would be easier to work with than the first.

    -- tom

    Comment


      #3
      RE: set report problem

      "example: 2a � 300 pcs
      and it does NOT have even ONE qty_out record for 2a."

      Yes, it does have one qty_out record, in the set. By definition, each parent record in a set creates a "set composite" record. It's just that all the fields in the child table for this record are blank. I think this is what is causing your troubles, because this blank value is matching other records incorrectly.

      Did you try creating a real child record with a qty_out of 0? You may have to code this into your application to get the calculations to be correct.
      There can be only one.

      Comment


        #4
        RE: set report problem

        dear tom/stan,
        sorry for delayed reply - was out of town.

        in the parent table the entry is specific - only one unique mtrl_in_no for every incoming inventory. however,
        the mtrl_out_no in the child may be many.
        to me this sounds like one to many.

        anyway, what stan suggested to make a record in dummy with zero values (in case there is actually no inventory out) worked.thanks stan.

        i really wonder why made it in a set when a single table for in & out could have been okay.

        thks & rgds,
        v.p

        Comment


          #5
          RE: set report problem

          VP,

          Sorry if I misunderstood your first post.

          You described a set with two tables, mtrl_in and mtrl_out. Because your calculated field for 'Balance' seemed to group records in both tables, based on their inventory id number, I assumed you would have multiple materials transactions in each table for each item in your inventory. That's many to many.

          -- tom

          Comment

          Working...
          X