Le 19/03/2020 à 18:43, Paul D. Mirowsky a écrit :
I agree with both Paul and Drew, Firebird is an excellent DB engine.
I have had recourse to fairly complex Firebird engine databases in a
client-server environment professionally for many years.
Alex
--
To unsubscribe e-mail to:
I hope that once you have HSQLDB working, you will transfer eventually
migrate to Firebird.
It has been far superior and and stable once I worked out the bugs.
https://wiki.documentfoundation.org/Documentation/HowTo/MigrateFromHSQLDB
Fair enough what people have said.
The one thing that hasn't been said is what you need to do with that that
it needs to be in a database.
Depending on what that is I may disagree with my colleagues and say go for
the firebird engine.
So - what are you hoping to get from the data in a database
Thank you Alex, Paulo and Drew.
I didn't realize there were so many "bugs" still to work out.
I'll stick with HSQLDB for now.
I trust there will eventually be a way to migrate to the new DB in the
future?
On Thu, 19 Mar 2020 at 10:10, Alexander Thurgood
wrote:
> Le 19/03/2020 à 13:32, bunk3m a
See below...
On 3/19/20 10:10 AM, Alexander Thurgood wrote:
Le 19/03/2020 à 13:32, bunk3m a écrit :
I would only recommend using embedded Firebird if you're comfortable
with all of its still numerous bugs, and are happy to get your hands
dirty correcting data types, lengths, etc and possibly
Le 19/03/2020 à 13:32, bunk3m a écrit :
I would only recommend using embedded Firebird if you're comfortable
with all of its still numerous bugs, and are happy to get your hands
dirty correcting data types, lengths, etc and possibly corrupted data.
Also, it is my understanding that there is
Thank you Alex and Drew.
I'll try your suggestions today.
I appreciate your help!
One more question if I might.
If I understand correctly, HSQLDB is being replace by Firebird. So I'd
like the engine to be Firebird so I don't end up with an issue in the
future.
How does one know that Firebird is
Le 19/03/2020 à 01:57, bunk3m a écrit :
As Drew has said, you can use your existing flat file in several ways :
1) Go via the empty ODB file method to drag the linked XLSX sheet from
your first ODB file to the second, empty ODB file and then follow the
import wizard.
2) Create an empty ODB file
On 18.03.2020 20:57, bunk3m wrote:
Hello all.
I thought I had gotten the data from a flat file (xlsx) into Base. I
was trying to import and create a new database.
My work requires my data to be in the company OneDrive. When I try to
open the connected flat file, I get errors that the file
