If you are using Microsoft Access 32-bit *.mdb database to store feature properties via MSLINKS, you may want to consider the following upgrade paths:
If this is simply not possible, and you are forced to continue using a 32-bit MDB database, you'll need to install 64-bit ODBC/OLE database drivers. These drivers are used by OpenCities Map CONNECT Edition as well as MicroStation CONNECT Edition which are both 64-bit applications. Since you are likely using 32-bit Microsoft Office, you will have to download the drivers separately.
Microsoft released a redistributable named "Microsoft Access Database Engine 2010 Redistributable". This package provides 32-bit or a 64-bit version of the Microsoft Access Database Engine, which includes the needed drivers. AccessDatabaseEngine_x64.exe can be downloaded from the Microsoft Download Center:
Microsoft Access Database Engine 2010 Redistributable
　
Note: If you already have 32-bit Office products installed, the installer will error and request that you uninstall it. Uninstall 32-bit Office, and rerun the installer.
After installing the Access Data Base Engine, you can then create an ODBC data source using the ODBC Data Source Administrator (64-bit) which is can be found in the following location:
C:\Windows\System32\odbcad32.exe
Finally reinstall your 32-bit Office product.
(To avoid installing the Microsoft Access Database Engine 2010 Redistributable package, simply upgrade your Office to 64-bit versions.)
Once the ODBC definition has been created, you can proceed to use it with OpenCities Map.
From the Database node, create a new database connection.
The database is read and the tables found in MSCATALOG are displayed in the Overview tab.
Create a new feature and add database properties:
Add SQL statements to keep the records in the database current and synchronized with the geometry in your design files.
If needed, remove the reference to MAPID from INSERT and COPY. For example, this:
INSERT INTO building (MAPID,MSLINK,buildingID,heatType,bldgType,occupClass) VALUES ([XFMGetMapId],[buildingMslink=XFMNextMslink("building")],[buildingID|NULL],'[heatType|NULL]',[bldgType|NULL],'[occupClass|NULL]')
Becomes this:
INSERT INTO building (MSLINK,buildingID,heatType,bldgType,occupClass) VALUES ([buildingMslink=XFMNextMslink("building")],[buildingID|NULL],'[heatType|NULL]',[bldgType|NULL],'[occupClass|NULL]')
Lastly, insert the feature placement metadata and test in a design file. There should be no errors when creating, copying, deleting features that use MSLINK to connect to an MDB to store its properties.
This workflow has been tested with the following: