[GLLUG] Moving from a Paradox database on Microsoft to Linux

Bernard Peek bernard.peek at gmail.com
Wed Jul 29 18:09:29 UTC 2020

That's a problem but it's manageable. If your data comes from multiple tables you do need to understand the relationships between them. You also need to understand the difference between tables and queries/views and the terminology used by both databases. Check which tables have indexes. Check whether the system you are extracting data from enforces any validation or business rules. That might be handled by code in data-entry forms.

I recommend importing raw data and adding keys and indexes afterwards. You may well find that adding those rules generates errors. If you get an error it's almost certainly because you haven’t understood the data. 

-----Original Message-----
From: GLLUG <gllug-bounces at mailman.lug.org.uk> On Behalf Of Martin A. Brooks via GLLUG
Sent: 28 July 2020 18:13
To: The mailing list for the Greater London Linux User Group <gllug at mailman.lug.org.uk>
Cc: Martin A. Brooks <martin at hinterlands.org>
Subject: Re: [GLLUG] Moving from a Paradox database on Microsoft to Linux

On 2020-07-28 17:40, John Winters via GLLUG wrote:
> Importing into any Linux database from a CSV file is easy-peasy and 
> can be accomplished in 5-10 lines of code.

That is almost certainly guaranteed not to work for any relational database as the relations will not be maintained.

More information about the GLLUG mailing list