Also, you can use the StarDesignor tool and through ODBC to Access, generate
the Sql for the database structure. You can then, examine the generated Sql
for reserved RBase words, etc. You can use the edited sql to create your
RBase db.
----- Original Message -----
From: "Gunnar Ekblad" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Tuesday, August 03, 2010 4:36 AM
Subject: [RBASE-L] - SV: Conversion
Dennis
Just a small tip.
Be aware that A**ess don't have same strong rules for column nanes and data
type. In the 2 A**ess MDB I worked with both had for example the column Name
ID in more the one table, for ex the first ID was customerID defined as text
the next ID was Article ID defined as integer. So make sure that you create
unique column names after the dataconversion and do table by table. As you
say Import/Export can be used. My preference was ODBC mainly because some
part are still in A**ess but with SCONNECT fro R:Base.
Gunnar Ekblad
Kontema IT AB
Hästholmsvägen 32
131 30 Nacka
Sweden
-----Ursprungligt meddelande-----
Från: [email protected] [mailto:[email protected]] För Dennis Fleming
Skickat: den 2 augusti 2010 20:32
Till: RBASE-L Mailing List
Ämne: [RBASE-L] - Conversion
Have a prospect that wants to move from A**ess to RBase.
Looks pretty straight forward using Import/Export, although I see
from the FTE article that you can also go the ODBC route.
A couple of years ago I made the mistake of converting a very old
RBase version to RB7 before validating the DB "design" and data quality.
Any do's/don'ts on making the MDB to RBx switch?
Thanks,
Dennis
*****
Dennis Fleming
IISCO
www.TheBestCMMS.com
Phone: 570 775-7593
Mobile: 570 351-5290
