Good morning,
you make a real hit!
/>The database for Company A should have all the tables used by the
users in Company A, including the low-volatility ones like your/
/>Municipalities table. If Comapny B needs Municipalities, it should
have its own copy. //_
_/
/_>You can create a DML script
He, Helen,
I don't understand as you have been able to believe that I have treated
a database as was a spreadsheet!!! I know what is a table, a database
(database as "set of tables", database as "file of type database"), a
relation, a key, an inedex, a... I've studied on your book.
When I spea
Antonio,
> I don't understand as you have been able to believe that I have treated
> a database as was a spreadsheet!!! I know what is a table, a database
> (database as "set of tables", database as "file of type database"), a
> relation, a key, an inedex, a... I've studied on your book.
> When
14.09.2018 20:08, 'Stellarancia.com' ni...@stellarancia.com [firebird-support]
wrote:
> My problem is that I've numerous programs that utilize one firebird file
> each.
All these programs can work with the same database. In contrast to DBF,
Firebird server
can be used by many programs withou
Antonio,
> I'm agree with you: all tables in a unique firebird file is the best choice.
> My problem is that I've numerous programs that utilize one firebird file
> each.
That problem is easy to solve. Place all of the tables in one
database and use an alias for that database in every applicati
He,
I'm agree with you: all tables in a unique firebird file is the best choice.
My problem is that I've numerous programs that utilize one firebird file
each.
There are tables that are drawn for a specific program, but there are
some tables that are "common" to all programs (example:
"munici
Hi,
1. Why not single Firebird database with all tables?
2. Why not recent Firebird which is FB3 not FB2.5?
Pozdrawiam,
Karol Bieniaszewski
