Sorry Robert, didn't mean to send to only you.
We're developing a management program that can manage several jobs that a
construction company is working on. We have a separate database for each
job that is installed in the program. This eliminates the need to keep an
extra field in each table t
Dan Greene
> -Original Message-
> From: robert_rowe [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 08, 2004 12:48 PM
> To: [EMAIL PROTECTED]
> Subject: Re: When does using multiple databases make sense?
>
>
>
> In our accounting software our users can mana
In our accounting software our users can manage the books for several different
companies with the same program. As such I have to keep a field (in every record) that
designates which company the given record is for and use it for report filtering,
lookups, etc. Had I used a different database
On 8 Jan 2004, at 04:12, Paul F wrote:
Greetings, I am wandering under what circumstances it is
sensible/beneficial
to use multiple databases for a single "project," and why.
The reason I ask is because I am re-developing an existing database
with
MySQL that someone else created with another en
