Well @PVince81 I see the point, but if we keep the old way, apps that use it, will still have the bug we try to resolve (meaning, if you add shares after you set the expiration date, they (new shares) will not have set the exp. date set in the db and therefor not expire). Should we just make the function throw an error if the argument list is too short, so calender app guys (and others that use it) see it when testing the app for the update and can fix it, instead of having it slip through the list of changes?