Message was edited by: Cyber Tan
It seems as you are using some alias and attempting to access dictionary information.
There is a chance that the DynLookup does not handle and/or support this.
You are probably better off contacting Technical Support.
Note that your where clause would never be false by the way, so your result set might not be what you expect it to be. That should not cause any weird behavior though.
Are you experiencing this from a client connected to an AppServer or from the AppBuilder session?
Just a quick guess: Is your AppServer started with the -zn startup parameter? Any messages in the AppServer logfile?
Mike
Message was edited by: Cyber Tan
Hi Mike,
This is at the Appbuilder session, even AppServer client session are having the same problem. Thanks.
Regards,
Tan
Hi Tan,
Given the fact that it works in the DynCombo there is a chance that this is a bug. We would appreciate if you took the time to report it to Support, so that we can take a closer look.
Note that I'm not sure what limitations exists when it comes to Dictionary access. The DynCombo has a simple task compared to the DynLookup, so it might just work by "accident".
Dynamics is not designed to support the database qualifier needed to reference tables that have the same name in multiple databases. This is a general limitation that also should apply to DynCombos and SDOs. (This limitation does not apply to SDOs in ADM2, so I assume there are ways to workaround this with static SDOs in Dynamics.)