Hi 2 all! A couple of days ago I read in some of the messages here how someone tried to pass names of <db-user name> and <table name> to a stored procedure and this way make it more flexible when it comes to target tables which are identical in structure, but might have been distinguished by their names, even might reside in different user spaces (might sound strange, but there's indeed need for such things).
Unfortunately I could not relocate this example and the SAPdb team's comments on that, instead I found indications that DBPROCs need information on user and table name as *identifiers*, not as *parameters*. This would force me to create the DBPROC declaration elsewise and declare it on the fly before using it, and, if need be, destroy it afterwards. a) Is it still true that DBPROCs don't accept <username> and <tablename> as parameters? b) Are there plans to extent the DBPROC functionality in this direction? c) In case this restriction is not yet lifted: Did anyone manage to find a neat workaround ? Any input welcome! Regards Dr. Michael Neuber living systems AG _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
