The connection via "MS Access" was not successful because MEMO fields bacame SQL Null [] fields with no content. As suggested in the OOo help I connected my existing MDB to a new Base via ADO link. It worked smoothly, however the MEMO field was now completely gone when I opened the table in Base. Frustrating...but I am not yet giving up on Base...
To make matters worse the connection deleted the memo field from my original MDB. No I did not save anything when I checked the tables in Base. The only save action was during establishing the connection. Luckily I had a 20hr old backup to restore the lost data.
Anyone out there with a fool proof method how to IMPORT data from an Access 2000 MDB into Base, please let me know. If I continue with Base, I need to rebuild the MDB functionality anyway.
Thanks
ADO link to Access 2000 MDB kills MEMO field
Re: ADO link to Access 2000 MDB kills MEMO field
Try with ODBC driver, create a new odbc data source from Control Panel > Administrative tools > ODBC data sources > New > Microsoft Access Driver > select your mdb file > OK. Launch Base, select connect to existing database > ODBC and insert the data source name you have chosen.
I don't know if it works with memo fields, I've never used them since I don't need to. However when testing a new application you should always avoid to work with actual data, just make a copy of your mdb file and save it on a separate directory on your hard disk.
A new version of ODBC driver is available from MIcrosoft web site, just run a google search for "Access Database Engine accdb", it should return the download link.
I don't know if it works with memo fields, I've never used them since I don't need to. However when testing a new application you should always avoid to work with actual data, just make a copy of your mdb file and save it on a separate directory on your hard disk.
A new version of ODBC driver is available from MIcrosoft web site, just run a google search for "Access Database Engine accdb", it should return the download link.
Re: ADO link to Access 2000 MDB kills MEMO field
thank you that worked, all fields are connected and contain data.
How do I "disconnect" from the data source MDB once I saved it in Base?
For some time I will have to develop/run both independently before I synchronize the data at a later point....perhaps... and switch to Base only.
How do I "disconnect" from the data source MDB once I saved it in Base?
For some time I will have to develop/run both independently before I synchronize the data at a later point....perhaps... and switch to Base only.
Re: ADO link to Access 2000 MDB kills MEMO field
You can disconnect your database from the Mdb file only copying tables into a new one, you can do it by creating a new empty Base file and dragging tables from the old one to the newer. A wizard will appear and will guide you through the copy process.
However I think this isn't the best solution, the ODBC driver is the fastest backend available under Windows. When I switched to Base I have simply copied my mdb files and I've started working on these using the ODBC connection.
However I think this isn't the best solution, the ODBC driver is the fastest backend available under Windows. When I switched to Base I have simply copied my mdb files and I've started working on these using the ODBC connection.
Re: ADO link to Access 2000 MDB kills MEMO field
The manual dragging into Base also works but it is tedious as you mentioned. Also the indexes from MDB are translated into long integers which breaks all the links in the relational database. No good.
I am just starting so hopefully only last question to this. If I just connect to the MDB all dats stays in the MDB, right? An independent Base would store everything in one .odb?
I am just starting so hopefully only last question to this. If I just connect to the MDB all dats stays in the MDB, right? An independent Base would store everything in one .odb?