Caroline, Don:
I have added a parameter UserPrivateCalendarPerPackageP to the calendar package.
It works as expected, at least that is what I thought for a few minutes.
The wrinkle and the problem:
Wrinkle: parameters are per package, so instances could set the parameter to conflicting values. In useage this shouldn't be a problem, at least I don't think. What could happen depends on when a user creates their first calendar, that is within what package. They could end up with two, or just one calendar if one instance is set to 1 and the other 0.
Problem: the calendar procs in the library procedures and on other pages wish to supply a package_id to the query which selects the calendars. This screws up the package which has the parameter set to 0, and didn't get to first create their own calendar. The package instance that did create a calendar works fine. So the issue is a rewrite of more pages, some with optional sql.
Ideas?
