bianchef
Posts: 17
|
| Posted: 01/01/2007, 1:40 PM |
|
how do I restrict a registered user to administer only one category?
so far, i have created a database, application and gui for a web calendar. the calendar has 18 categories (schools) and 18 registered users (school webmasters). the calendar has a drop down list for a public user (parents) to choose one of the categories to view its corresponding calendar. the default view is to display events from all categories for public users (who are not registered users). all of these conditions are components working ok.
what i need now is somehow to restrict each of the 18 registered users to access and administer only one of the 18 categories, that is only the category (school) that is assigned to their registration (as administer of the calendar).
for example, registered user "abcschool" , who is registered as an administrator level, can only administer (view, insert, update, delete) the category called "abc elementary school" so he/she can administer only that category and not the remaining calendars.
as i have it now, all registered users can access/administer all 18 categories (schools).
any ideas? and code samples?
my environment is:
IIS 5.1, ASP.Net 2.0, SQLServer 2000, CodeCharge Studio 3.1
my application is:
VCalendar (1.1.6) with project file calendarVB.ccs
.NET 2.0 + MSSQL
|
 |
 |
Edd
Posts: 547
|
| Posted: 01/01/2007, 5:03 PM |
|
bianchef,
I have just completed the same thing for 2 of my clients, the only way to do the method that you want to pursue is to create an reference table that ties the categories to users where one category can be updated by x number of users and visa versa.
I have to warn you that after we built the above method we found that schools cross associate the work that they do and it broke the method that you are pursuing. We then changed the strategy where people can add / delete to any category but their entries can be locked / unlocked from other users. This seemed to work the best as work was protected and could be expanded by other parties.
Edd
_________________
Accepting and instigating change are life's challenges.
http://www.syntech.com.au |
|
|
|
bianchef
Posts: 17
|
| Posted: 01/02/2007, 8:11 AM |
|
Thanks for suggesting a user and lock strategy.
Would you provide the design steps or code sample on lock/unlock a calendar entry? (I am new to CodeCharge Studio and learning the tips and tricks.)
|
|
|
|
Edd
Posts: 547
|
| Posted: 01/02/2007, 5:27 PM |
|
The Lock / Unlock is just a flag in the database which can be set in the data entry screen and shows that an entry is locked to the creator of the entry.
I should note that my app was written in CCS 2.3 so it doesn't use the Calendar object in CCS 3.0 - it was a handcoded asp class object.
If you send me a private message with your email address I will send you some screen shots to get you started.
Edd
_________________
Accepting and instigating change are life's challenges.
http://www.syntech.com.au |
|
|
|
|
