"Ann W. Harrison" <aharrison@...> wrote:

>
> a procedure created when a field was a string should continue to work
> even if that field was changed to something else. As above, if the
> change goes from a less restrictive type to a more restrictive type,
> then give conversion errors.

For changed dependency fields, it works. For procedure parameters - it
doesn't, as we get a message format mismatch.


Dmitry