Importing CCMDB.accdb into a new .accdb: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →Steps |
Ttenbergen (talk | contribs) m →Steps |
||
| Line 12: | Line 12: | ||
#* Document Window Options "Overlapping Windows" | #* Document Window Options "Overlapping Windows" | ||
# add VBA tools references: | # add VBA tools references: | ||
#* Microsoft Excel | #* Microsoft Excel 16.0 Object Library (used by converters function age) | ||
#* Microsoft Visual Basic for Applications Extensibility 5.3 '''(can't remember what for, leaving out for now...)''' | #* Microsoft Visual Basic for Applications Extensibility 5.3 '''(can't remember what for, leaving out for now...)''' | ||
#* Microsoft ADO Ext. 6.0 for DDL and Security '''(can't remember what for, leaving out for now...)''' | #* Microsoft ADO Ext. 6.0 for DDL and Security '''(can't remember what for, leaving out for now...)''' | ||
Latest revision as of 10:48, 2023 January 17
These are just some notes for Tina, probably not relevant to anyone else.
.accdb files occasionally become corrupted and bloated. Compact and Repair only deals with some of it, so another recommended solution is to import all the contents of a db into a new, clean DB. Some settings do not travel across with this import, so this is a checklist of what else needs to be done when importing into a new .accdb.
Steps
- set up new db
- import all tables etc
- set current database options
- compact-on-close
- database title "Critical Care and Medicine Database"
- display form "Main Form"
- Document Window Options "Overlapping Windows"
- add VBA tools references:
- Microsoft Excel 16.0 Object Library (used by converters function age)
- Microsoft Visual Basic for Applications Extensibility 5.3 (can't remember what for, leaving out for now...)
- Microsoft ADO Ext. 6.0 for DDL and Security (can't remember what for, leaving out for now...)
- close
- open in exclusive mode, set password (ignore row... cipher... warning)
Related articles
| Related articles: |