Thanks for the tips on converting MDB to Rbase.
The prospect is sending us their data base next week and I will have a chance to "validate the design". Although they must provide the same periodic reports to a government agency as my current customer, I suspect I will not have apples and apples. Probably more like kumquats and artichokes.
Thanks Again,
Dennis
*****
At 04:36 AM 8/3/2010, you wrote:
Dennis
Just a small tip.
Be aware that A**ess dont 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
Dennis Fleming
IISCO
Phone: 570 775-7593
Mobile: 570 351-5290
