![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I've finished up designing a database and as it is my first as a paid consultant, I'd like to be sure I am covering myself, and the security of the layouts. Any recommendations would be very welcome. So far I have the following in place.... Criticism welcome :-) 1. Filemaker 8.5, OSX - will also be used by Windows platform...testing completed for window/font compatability. Has any one come across other major issues when cross platform? 2. Three main levels of permissions set. __MGMT: Records (full access); layouts (view all, modify records in all); value lists (access only to those with custom values (not pulled from tables)); scripts (no access) - allow printing, exporting, data validation override, and modify password, access to all menu commands __SPVS: Records (deletion only permitted where creation is premitted); Layouts (view most, modify most - based on criteria for 2nd level mgmt); Value Lists (access only to those with custom values 2nd level mgmt); scripts (no access) - allow printing, exporting, and modify password, access to all menu commands __Basic User same as SPVS without the access to value lists and few other tables etc. __Admin: Full access 3. Database is going to reside on server with software loaded on four workstations with access to ftp. Are there any known issues I should review with the server manager? Firewall concerns? Curious how I did timewise on this project...spent about 40 hours total in development (not including pre planning with client - add another 15 horus there). Lara |
#3
| |||
| |||
|
|
On Mar 1, 9:39 am, "Carpeflora" <l... (AT) liquidpointdesign (DOT) com> wrote: I've finished up designing a database and as it is my first as a paid consultant, I'd like to be sure I am covering myself, and the security of the layouts. Any recommendations would be very welcome. So far I have the following in place.... Criticism welcome :-) 1. Filemaker 8.5, OSX - will also be used by Windows platform...testing completed for window/font compatability. Has any one come across other major issues when cross platform? 2. Three main levels of permissions set. __MGMT: Records (full access); layouts (view all, modify records in all); value lists (access only to those with custom values (not pulled from tables)); scripts (no access) - allow printing, exporting, data validation override, and modify password, access to all menu commands __SPVS: Records (deletion only permitted where creation is premitted); Layouts (view most, modify most - based on criteria for 2nd level mgmt); Value Lists (access only to those with custom values 2nd level mgmt); scripts (no access) - allow printing, exporting, and modify password, access to all menu commands __Basic User same as SPVS without the access to value lists and few other tables etc. __Admin: Full access 3. Database is going to reside on server with software loaded on four workstations with access to ftp. Are there any known issues I should review with the server manager? Firewall concerns? Curious how I did timewise on this project...spent about 40 hours total in development (not including pre planning with client - add another 15 horus there). Lara Have you logged on in each of the Privilege Sets and attempted to use the solution as it is intended to be used by those Privilege Sets? What about trying to use the solution in ways it was not intended to be used? G |
#4
| |||
| |||
|
|
On Mar 1, 12:26 pm, "Grip" <g... (AT) cybermesa (DOT) com> wrote: On Mar 1, 9:39 am, "Carpeflora" <l... (AT) liquidpointdesign (DOT) com> wrote: I've finished up designing a database and as it is my first as a paid consultant, I'd like to be sure I am covering myself, and the security of the layouts. Any recommendations would be very welcome. So far I have the following in place.... Criticism welcome :-) 1. Filemaker 8.5, OSX - will also be used by Windows platform...testing completed for window/font compatability. Has any one come across other major issues when cross platform? 2. Three main levels of permissions set. __MGMT: Records (full access); layouts (view all, modify records in all); value lists (access only to those with custom values (not pulled from tables)); scripts (no access) - allow printing, exporting, data validation override, and modify password, access to all menu commands __SPVS: Records (deletion only permitted where creation is premitted); Layouts (view most, modify most - based on criteria for 2nd level mgmt); Value Lists (access only to those with custom values 2nd level mgmt); scripts (no access) - allow printing, exporting, and modify password, access to all menu commands __Basic User same as SPVS without the access to value lists and few other tables etc. __Admin: Full access 3. Database is going to reside on server with software loaded on four workstations with access to ftp. Are there any known issues I should review with the server manager? Firewall concerns? Curious how I did timewise on this project...spent about 40 hours total in development (not including pre planning with client - add another 15 horus there). Lara Have you logged on in each of the Privilege Sets and attempted to use the solution as it is intended to be used by those Privilege Sets? What about trying to use the solution in ways it was not intended to be used? G Hadn't thought of that...der THANK YOU! |
#5
| |||
| |||
|
|
I've finished up designing a database and as it is my first as a paid consultant, I'd like to be sure I am covering myself, and the security of the layouts. Any recommendations would be very welcome. So far I have the following in place.... Criticism welcome :-) 1. Filemaker 8.5, OSX - will also be used by Windows platform...testing completed for window/font compatability. Has any one come across other major issues when cross platform? 2. Three main levels of permissions set. __MGMT: Records (full access); layouts (view all, modify records in all); value lists (access only to those with custom values (not pulled from tables)); scripts (no access) - allow printing, exporting, data validation override, and modify password, access to all menu commands __SPVS: Records (deletion only permitted where creation is premitted); Layouts (view most, modify most - based on criteria for 2nd level mgmt); Value Lists (access only to those with custom values 2nd level mgmt); scripts (no access) - allow printing, exporting, and modify password, access to all menu commands __Basic User same as SPVS without the access to value lists and few other tables etc. __Admin: Full access 3. Database is going to reside on server with software loaded on four workstations with access to ftp. Are there any known issues I should review with the server manager? Firewall concerns? Curious how I did timewise on this project...spent about 40 hours total in development (not including pre planning with client - add another 15 horus there). Lara |
![]() |
| Thread Tools | |
| Display Modes | |
| |