Multi Company Setup

[Ray]

Hi All,

I would like to get a fresh look at what I need to do.

I want to setup a multi company that has multiple sites/locations under a given company, what I thought of doing is making a table for the sake of argument registored_user_header then link that table to a table called location_detail.

Then I would make a set with the registerd_user as the header table in the set then link the rest of the application off the location_detail.

I am rebuilding an application from the ground-up that I can use on the new WAS when it becomes available to host the
application on the internet.

What are your thoughts please-?
-Ray

[Cheryl Lemire]

RE: Multi Company Setup

Hi Ray,

Is the general data going to be shared by all locations, or do they have their own individual data besides location? There are several ways to accomplish what you want depending on exactly what your end results needed are.

If you simply need addresses, etc for report and form purposes you can create a table to hold that data and use variables on your report and form fields.

You can create a location table that all your other tables use a lookup for, ie one employee table with all the employee records that includes a field for lookup from the location table.

With this scenario you would basically have a location table and a company information table added to your existing table structure.

If the different locations are not sharing any data then completely separate databases is the best resolution.

Just an opinion.

Cheryl

[Ray]

RE: Multi Company Setup

Hi Cheryl,

Thank you for your reply,

Think of what I want to do as an online banking application
when you go to www.mybank.com and click sign-in you are presented with only your account information this would be one part of my application but to add to this a I want the customer after they sign-in to have their own set of data
then on top of that each company has multiple locations with their own set of books.

The way I see the structure is company_sign_in link
one-to-many to the company_location table one_to_many
link to the rest of the application from their.

When I do a story board on paper this looks good but I wondered if anyone else could give this a fresh look and maybe they will see something wrong with this design that I don�t because as we all know it's better to try and catch it on paper then when your half way threw development.


Hope I am clear
Ray

[Scott Emerick]

RE: Multi Company Setup

Ray,

In a simplified form ....

Have a global variable set with the company ID and have a field in your tables "Company_ID"

Then just match the global variable that was set on selecting a company and/or login and either link or filter the records accordingly.

Scott

[Ray]

RE: Multi Company Setup

Hi Scott,

Thank you for you suggestion I will keep this method in mind.

-Ray

[Cheryl Lemire]

RE: Multi Company Setup

Hi Ray,

OK, it sounds like one database to me with multiple additional tables needed. I have a very similar structure setup with inventory control if I am understanding you correctly.

You need to create tables with user information and access level information. You will need a login page which will capture specific identifiers as session variables. You will later use these various session variables to determine what the current user has access to based on query filters etc.

In my inventory db I have multiple companies inventories setup. They are separate companies with different users, but I have them all in one database. By requiring the login and capturing session variables I can then discriminate against which company inventory files that user is allowed to view.

Some individuals will access only one company, others will access multiple companies, and yet others will be able to access all company inventory information.

I hope this helps.

Cheryl

[Ray]

RE: Multi Company Setup

Hi Cheryl,

That is correct so my way of thinking seems write to you?

-Ray

[Peter.Greulich]

RE: Multi Company Setup

Ray,

To diagram it as if it were a set:

Parent_Company===1:M===Child_Companies===1:M====Application Tables

Of course, it doesn't have to be a set, but the above is one concept. In the above scenario, each child company shares the same application tables, differentiated by a unique ID. Although, strictly speaking, you could just have:

Parent_Company ~ stand alone table
Child_Companies===1:M====Application Tables

It all depends on how the relationship between entities functions.

Peter

[Ray]

RE: Multi Company Setup

Hi Peter,

Thank you for taking the time to respond to my question,
so my way of thinking is correct I just wanted to be sure.

-Ray

[Ray]

RE: Multi Company Setup

Hi Cheryl,

If you would not mind providing me with information on how
you made the set/sets for this setup I have been pulling my hair out all day Saturday I think I am almost their but I would like a fresh look at the setup to see if I can improve the way I did this.

My requirements are as follows, I have a site_ID table with
required info for a particular company to log-in to their site then I have a subsite_ID table because each site can
have multiple locations for a given site then what ever info I need to share site_ID wide I link off the site_ID
table.

I have made one big set with the site_ID table as the
parent and from hear follow your setup.

-Ray