Hi, The dependency tables would be useful only if we want to keep same AMI-code (dll) and just change the dependency outside of the code using .ami file. However, I do not see this as common use-model - I would assume that all such dependency should be handled inside of c-code (Algorithmic...) and that we should avoid overloading of .ami file such tables. AMI-code should be able to handle such dependency by coding the right values for dependent parameters based on Key parameters in ami file. Please let me know if I am missing a use-case where this cannot be handled inside the dll. rgds ..kukal Taranjit Kukal | Product Engineering Architect P: 91 120 3984000 www.cadence.com<http://www.cadence.com/>