Well Dennis That reminds me in MDB you cant relay on columns names being the same in primary key and foreign key, so you better control it yourself. I am only saying that the sound naming conventions, is not as sound as I would like to be in B.lls MDB DB.
In mY case I hade an ID inte Master that in a lower table was Car_id. It was the same but not named the same. 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 3 augusti 2010 16:59 Till: RBASE-L Mailing List Ämne: [RBASE-L] - SV: Conversion Gunnar, 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 <http://www.thebestcmms.com/> www.TheBestCMMS.com Phone: 570 775-7593 Mobile: 570 351-5290
