Ed: I know this is a simple suggestion, but have you tried tracing to see
which lines of code are giving you those error messages? At the r> prompt,
type SET TRACE ON, then edit using your external form. Then evaluate
whether those error messages are valid or not.
Karen
> Rachel,
> Good suggestion. I created a Test external form and placed two bit buttons
> on it. The
> first has an exact copy of the macro code in the eep. The other has a call
> to the macro.
>
> Executing either gives me the same result as calling the macro from the
> xxxx.rba;
> i.e. 4 warning messages that "No Rows Exist or Satisfy Specific Clause
> (2059) followed
> by an Error message that "No Rows Exist or Satisfy Specific Clause (2059)
>
>
> In the macro, error messages are currently turned on hence all the
> warning/error messages.
>
> Bottom line is that I've eliminated the xxxx.rba as a potential issue.
> Suggestions of how
> to get closer to the heart of this?
>
> Thanks,
> Ed
>
