This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
how_to:generateamtdb [2012/02/29 11:57] 132.168.73.124 |
how_to:generateamtdb [2012/02/29 12:01] 132.168.73.124 |
||
---|---|---|---|
Line 40: | Line 40: | ||
===== AMT database model ===== | ===== AMT database model ===== | ||
- | + | When creating an AMT database (MS Access) from hEIDI, following tables are populated: | |
- | Below is the actual AMT database model showing relationships between tables in MS Access.\\ | + | |
- | + | ||
- | When exporting an AMT database from hEIDI, 5 tables are populated: | + | |
* **__Table AMT__**: species of the exported User context | * **__Table AMT__**: species of the exported User context | ||
Line 81: | Line 78: | ||
* delay_minutes: analysis delay in minutes | * delay_minutes: analysis delay in minutes | ||
- | UMCs tables are populated when using '[[how_to:includeumcinamtdb|Read UMCs]]' tool. | + | :!: **Notes**: |
+ | * UMCs tables were populated using '[[how_to:includeumcinamtdb|Read UMCs]]' tool until hEIDI 1.12.0.\\ | ||
+ | * Since hEIDI 1.13.0, UMCs result files are included into MSIdb (instead of AMTdb) | ||
{{:how_to:amtexport_relationsmsaccess.png|Relationships in the AMT database (MS Access)}} | {{:how_to:amtexport_relationsmsaccess.png|Relationships in the AMT database (MS Access)}} |