Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Ken Murphy
  Where is Ken Murphy?
 Springhill
 Canada
 Ken Murphy
 To: Kulwant Singh
  Where is Kulwant Singh?
 Shimla
 India
 Kulwant Singh
 Tags
Subject: RE: Better Multiuser Approach?
Thread ID: 112501 Message ID: 112513 # Views: 4 # Ratings: 0
Version: Visual FoxPro 6 Category: Visual Basic
Date: Thursday, November 09, 2006 8:06:18 AM         
   


> > > Hello all,
> > >
> > > Thanks for your help with my previous postings.
> > > Can someone please guide me regarding:-
> > > How to go about automation of an organisation with three Departments in the same building (on Lan).
> > >
> > > Approach One.
> > > Keep Data at one cpmputer. Other computers Access 'this' computer for the transactions.
> > >
> > > Approach Two.
> > > Keep independent Data at each computer. At Day close : Gather and consolidate data from all Nodes.
> > >
> > > Which approach should be adopted? What are the Pros and Cons of each? Are there other better alternatives?
> > >
> > > Thanks!
> > > kulwant

> >
> >
> > There is no question in my mind. 3 departments close to each other. The first is te way to go. That way everyone has and works with live data.
> >
> > Approach Two involves too much compilcation to even contemplate. Forget it. Keep your data as live as is possible always.
> >
> > IMHO

>
> Thank you Sir,
> Would your answer be any different considering:
> All three departments are selling different products, with no concurrency issues involved.
> The only need for consolidation is that the management needs a a Consolidated/Summarised report of preceedings at each Department.
>
> thanks!
> kulwant


Kulwant,

Bernard is absolutely correct. Save the data in one location. Use a server if at all possible. If your budget does not permit you to use a server, then set one machine (the fastest and least used) as the central repository for your data. When you think about this for a while you will see the benefits. For example, just think about the backups. If you had three databases, you would also need three backups - not good.

Your company may be organized into three departments today, but what happens in the future? Will they be consolidated into one department? Will your company expand and will you now have five departments? This could get very cumbersome very quickly.

If you use a centralized database, everybody can look at the same "Product" table. You can add a "ProducingDept" field to the product table and then filter records based on that field. If you are in Dept. 1, you get to look at products that are produced in Dept. 1. When you wish to create a consolidated report, you simpy subtotal by dept. If you had three databases, you would have to query all three and then consolidate the results into a single cursor. If you expand your company and you now have five departments, with a single database, your report still works. With multiple databases, you need to modify the program to query those new databases.

Definately go with option 1.

Ken
You shall know the truth - and the truth shall set you free. (John 8:33)

ENTIRE THREAD

Better Multiuser Approach? Posted by kulwant singh @ 11/9/2006 6:37:22 AM
RE: Better Multiuser Approach? Posted by Bernard Bout @ 11/9/2006 7:07:19 AM
RE: Better Multiuser Approach? Posted by kulwant singh @ 11/9/2006 7:30:51 AM
RE: Better Multiuser Approach? Posted by Ken Murphy @ 11/9/2006 8:06:18 AM
RE: Better Multiuser Approach? Posted by Resty Jr Masilungan @ 11/9/2006 10:42:20 AM
RE: Better Multiuser Approach? Posted by Ken Murphy @ 11/9/2006 1:05:29 PM
RE: Better Multiuser Approach? Posted by Bernard Bout @ 11/10/2006 10:38:50 PM
RE: Better Multiuser Approach? Posted by Bernard Bout @ 11/10/2006 10:35:34 PM