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

How did/would you handle this

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

  • How did/would you handle this

    In an multi tennant application, there are vendor companies who sell product, and buying companies buying from the vendors. Lets call the app. owner and system opperator "the system". The vendors are the system's customers that pay the system to be represeented, the buyers are the vendors customers.

    Original thinking was to keep the system's customers separate in a Vendors table, and the buying companies separate in a Customers table, (customers of the vendors). I thought this would make it easier overall with fewer filters and less likely to overlook something when constructing grids and so on, and when the system wants to work with its own customers -the vendors. Also maybe faster not having to always filter out either vendor or customer records. There would be a proportion of 2,000 customers per vendor, 25 vendors would be 50,000 customer records. This brings up the problem of creating an auto increment id for the vendors that would not duplicate the id for the vendor customers.

    The other solution would be just one Company table holding the vendor and customer information with a "classification" field identifying either vendor or customer. The Id number problem is solved but a lot of carefull filtering will always have to be done. I know the id problem with two tables is not a problem, its just deciding on how one wants to id the records.

    If you have faced this question before, what did you decide and why. Also if anyone has an opinion, please feel free to express it. Would you lump the system's customers(the vendors) into the same table with the vendors customers, or keep them separate?

    Thanks,
    John

  • #2
    Re: How did/would you handle this

    Maybe in your case link the table to itself? One table, no id conflicts. Add a linking field so you can link back to yourself.
    Peter
    AlphaBase Solutions, LLC

    Peter@AlphaBaseSolutions.com
    https://www.alphabasesolutions.com


    Comment


    • #3
      Re: How did/would you handle this

      Thank you for your reply.

      If I understand correctly, this would create two grids?
      One with my customers, the vendors, and another grid with the vendors' customers?
      Would your suggestion create a parent and linked child grids?
      Wouldn't this involve the use of filters?
      Would I be able to access just the linked child grid directly without first having to open the parent grid?

      Isn't this the same as one table and calling grids using filters to filter out/in records?

      John

      Comment


      • #4
        Re: How did/would you handle this

        You can probably use one grid linked to itself. But, if that seems redundant use two grids. You must add a linking field, so your table structure would look like this:

        Id Company Linking_ID
        1 Acme Inc
        2 Alpha Software 1
        3 Ace Hardware
        4 Home Depot 3
        5 Lowes 3

        So in this example, Alpha Software is a child of Acme Inc and Home Depot & Lowes are childs of Ace Hardware.
        Peter
        AlphaBase Solutions, LLC

        Peter@AlphaBaseSolutions.com
        https://www.alphabasesolutions.com


        Comment

        Working...
        X