Re: Proper use of database splitting
From: PC Datasheet (nospam_at_nospam.spam)
Date: 01/04/05
- Next message: Rick Brandt: "Re: Lost Toolbar during splitting"
- Previous message: iholder: "Re: creating a pop-up page"
- In reply to: Howard: "Re: Proper use of database splitting"
- Next in thread: Howard: "Re: Proper use of database splitting"
- Reply: Howard: "Re: Proper use of database splitting"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 04 Jan 2005 21:19:20 GMT
If the data in the product, supplier, resource and other lookup tables is
relatively static, make a copy of the database with these tables for each
sales rep and use it as the backend for each sales rep. Create a template
customer mdb for the front end and link to the backend database. When a
sales rep gets a new customer, all he needs to do is make a copy of the
customer template database and he can then immediately record the new
customer's data. When the template is copied, the links to the backend will
stay intact so the sales rep does not have to do anything about linking to
the backend. Since the new database is for one customer, all the sales rep
needs to do is delete the mdb file when he no longer needs that customer's
data. As long as the tables in the master backend stay the same albeit new,
edited or deleted data, the backend database for each sales rep could easily
be replaced with a copy of the master backend; nothinh more would need to be
done.
I could automate this whole process for you through a user interface to make
it user friendly for all involved. If you would like my help to do this,
contact me at my email address below.
--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
resource@pcdatasheet.com
www.pcdatasheet.com
"Howard" <Howard@discussions.microsoft.com> wrote in message
news:B5341FDC-4CAA-46C5-A3E0-0C9502246F5E@microsoft.com...
> Hi!
> I appologize, I haven't been clear. There is more involved than just being
> able to delete a customers entries. I am familiar with Cascading. Having a
> separate database for each customer would satisfy my client's criteria to
> take the database on the road with several mobile sales reps. If each
sales
> rep takes a copy of the entire database, then creates a new client and
adds
> all the item and labour records for that customer, synchronzing data back
at
> the server will
> be a nightmare. A separate database for each customer will be ideal, but
> with shared product, supplier, resource and other lookup files. Users can
> then just pass a customers database back and forth for updating without
any
> duplication or synchronization problems. I've seen huge tax and accounting
> programs developed this way so client records can be shared amongst teams
of
> mobile accountants. Same as a doctors office with a file for each patient.
> Please let me know if there is an efficient way to keep each customers
data
> as a separate mdb file. Thanks!
> -Howard
>
>
>
> "PC Datasheet" wrote:
>
> > If your tables are designed correctly and the proper relationships are
> > setup, you should have Cascade Delete enforced between CustomerID in the
> > customer table and CustomerID as the foreign key in all other customer
> > related tables. Deleting a customer table then in the customer table
wou;d
> > automatically delete that customer's records in all related tables.
> >
> > --
> > PC Datasheet
> > Your Resource For Help With Access, Excel And Word Applications
> > resource@pcdatasheet.com
> > www.pcdatasheet.com
> >
> >
> > "Howard" <Howard@discussions.microsoft.com> wrote in message
> > news:40076A05-FEFA-4C50-8B1B-E8F8791DA948@microsoft.com...
> > > Hi!
> > > Through this forum, I have just learned how to split my database into
data
> > > (tables) and application (everything else). My application would be
ideal
> > if
> > > I could have a seperate back-end database for each customer, as each
> > project
> > > is short term, then the data for that customer is not required, so it
> > could
> > > be deleted. Also sometimes after the project is created for a
customer,
> > the
> > > sale goes sour and the information for that customer is again not
> > required.
> > > Could I create a "template" backend database, copy and rename it
> > > appropriately for each customer, then use the File->Get External
> > Data->Import
> > > functionality to switch between databases (customers), or is it really
not
> > > meant for toggling between databases and might corrupt things. Please
let
> > me
> > > know.
> > > --
> > > Thanks!
> > > -Howard
> >
> >
> >
- Next message: Rick Brandt: "Re: Lost Toolbar during splitting"
- Previous message: iholder: "Re: creating a pop-up page"
- In reply to: Howard: "Re: Proper use of database splitting"
- Next in thread: Howard: "Re: Proper use of database splitting"
- Reply: Howard: "Re: Proper use of database splitting"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
