At 10:28 AM -0500 11/2/00, Melissa Victory wrote:
>Okay, another question. My company wants to have two databases,
>based on ebase, running simultaneously on the same server. Does
>this pose any problems with the rest of the ebase files (i.e. all of
>the .102's)?
>
Do you mean you will be running two COMPLETE SETS of the ebase files?
The files are related and don't work individually. Sorry if that
sounds elementary, but "...problems with the rest of the ebase
files..." sounds like you intend to try to run part of the set.
If that's the case, think about why you want two sets. Different
organizations? If it is just different segments of the constituency
of the same organization (members and prospects, for example) you
should combine them and code the segments. Otherwise you're bound to
end up with the same person in both lists.
If you really need to run two sets, there is no technical problem.
You might confuse the humans, though. The files in both sets will be
named the same. There is great danger of getting them intermixed
during troubleshooting or other admin functions. In short, possible
but bad practice.
--
Dave Shaw Northwest Classics, Inc
tel: 206-954-7526 fax: 206-625-1338
