Ray,
First, don't hijack threads!!

At 01:38 PM 11/11/2004 -0700, you wrote:

>I am starting to move all the in-house apps to Firbird. They have been
>running on Clipper and Paradox database systems.
>
>My question is this...
>
>How do I structure the new Database? Do I have one single fdb file and
>just throw all the tables in the same db, or do I split it out into
>some logical transaction based groupings?

One single FDB file. Firebird isn't a file-served database: the server
manages your database inside a single logical file, which can be one or
multiple files on disk. There is no way to access the files individually,
nor even to know "what is where".

Don't split it into separate databases, either. You can't query across
database boundaries and you can't relate tables that live in separate
databases.

>If I split it into multiple fdb files can they all reside in the same
>directory or should I seperate them into different subdirectories.

Whether you split or not depends on the file limits applicable to your
operating system. The database server doesn't mind whether you have one
file or many and it doesn't mind if they are on separate
partitions. However, in this day and age, there's no reason to split a
database across partitions. If a database is too big to fit on a single
partition, you'd be into RAID territory and, on RAID arrays, you won't even
know where your physical database file(s) is/are located.

>Right now the Firebird server is on MS 2000 server but we will be
>moving them to a Linux server as soon as our IT guy can get the server
>built. (You know how those IT guys are busy putting out fires)

If your partition on Win2K is FAT32 then the file size limit is 2 Gb. But
why would you put a database on a FAT32 partition? A Win2K NTFS partition
can take a file of unlimited size, so you can begin with a single database
file and, later, split it when restoring to Linux if the chosen filesystem
on the Linux partition has a 2 Gb or 4 Gb limit (some do).

./heLen