|
Security wise, the multiple members concept seems more practical
than company key-field. Personally, however, I'd be much more
comfortable with separate libraries & files for each company, which
could be secured as required. Really, though, I all depends on the
situation.
Eric DeLong
______________________________ Reply Separator _________________________________
Subject: Re: Optimized Search method for DB files. ?
Author: <MIDRANGE-L@midrange.com > at INET_WACO
Date: 10/22/98 12:29 PM
Instead of combining data from multiple companies into the same file,
have you considered using multiple members? (ie) A member for each
company. Depending on the company you want to work with, a CL can set up
appropriate overrides.
Ravi
Prabhu.Chella@smed.com wrote:
>
> I need some help, in deciding the best method for accessing ,
> searching(chaining etc. etc ) a huge database.
>
> Actually we have a plan to introduce a concept, wherein the DB might
> contain data from more than one company in the same AS/400 DB.
> Say, If the DB of each Company had Employee first name, last name
> ....... Now it would have an additional
> field(1'st key field in all the DB's) which will determine to which company
> the data belongs to .
>
> E.g. Before 2 companies say A and B had data like this
> A:
> Mark Smith
> Timothy Dalton
> B:
> Thomas Cook
> Edwin moses
>
> Now it would be in a single DB in a common place ..
> (New
> Field)
> 100 Mark Smith
> 100 Timothy Dalton
> 200 Thomas Cook
> 200 Edwin Moses
>
> So now the size of the database will be increasing by the no of companies
> combined together. The Size of the DB will be very large in most of the
> cases (We need to optimize the accessing, searching of these DB's).
>
> Can anyone help us out by providing some good tips for tackling this
> problem !!!!! ..
>
> Thanks in Advance ,
> Chellaprabhu.
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.