Calling a database object belonging to another component/module from Developer Studio produces a 'No Dependency Found' error, even after clearing and refreshing the code-completion cache.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This needs Dynamic Component Dependency conditional compilation around the cross-component call, rather than referencing the other component's object unconditionally — wrap the relevant code in a conditional-compilation block that checks whether that other component is actually installed (the framework's generated Component_<ModuleName>_SYS.INSTALLED flag) before compiling in the call to it. This is the standard pattern for safely calling into another component that may or may not be present in a given environment, and resolves the 'No Dependency Found' compilation error.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions