Hi Group,
we've noticed that Visual Studio.NET 2003 does not seem to be capable of
reading the parameter data for commands on oracle stored procedures that
are collected in packages.
We can create a command, change the command type to StoredProcedure and
enter a stored procedure or function name and it works fine (same
functionality as simply drag'n'dropping the stored procedure or function
from the server explorer to the designer). That works smoothly.
However, when we enter a function name from a package, the name cannot
be resolved. It works fine during runtime, when we have manually added
the parameters (so there is no spelling problem with the names) - but
the designer simply doesn't find the stored procedure or function.
Is this a known problem? Are there any workarounds? What we're
considering is creating temporary stored procedures (not in a package)
to automatically get the parameters, and then manually changing the name
so that it referes to the original function stored in a package.
This is still easier than manually entering the parameters - but still
it's rather cumbersome and time consuming...
regards,
david
--
Auch das geht vorüber. (Sufi-Weisheit)
Holger (David) Wagner Tel: +49 (89) 890 50 962
Dewetstrasse 1 Mobil: +49 (177) 274 12 45
D-80807 München Fax: +49 (177) 992741245