With my short term memory deficit (due to an auto accident 14 years ago)
and limited programming capabilities compared to most on the forum, there
is no such thing as a simple suggestion. All suggestions become good ones.
Case in point. Using the external form to execute this macro with SET TRACE
ON, it quickly became obvious that my problem was that the append statement
wasn't working early in my macro when called from the external form or .rba.
Changing the macro to project the data into a new table and then use a string of
ALTER TABLES to add the necessary additional columns solved it.
Why a simple Append isn't working when the macro is called rather than when it
is executed from the R> prompt is a mystery to me. More importantly the problem
is solved thanks to the combined suggestions of yourself, Rachel, and some
behind the scenes assistance from Bernie Lis.
Thanks to all. Onto my next feeble challenge....
A good weekend to all.
Ed
May 20, 2010 09:24:07 AM, [email protected] wrote:
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
