Hi David, Barry is right and his answer is much better than what you could get with any client connecting to the data. You can define read-only access for some users and write access to other users both at the database level and at the shared disk level. All the examples you gave (below) are normally managed this way. This is the only safe way to do it: if you create a new client software managing access restriction, you may always face users using other clients to workaround those restrictions. On the contrary, whatever the client you use, nobody will break a well designed database or shared disk security. The only part of the access restrictions that a client as QGIS should take care of is to ask users to provide a correct username/password, and this is implemented.
Hope it helps. Mayeul Le mercredi 16 mars 2011 à 16:21 -0500, David Silva Barrera a écrit : > For example an Analist just view and calculate areas and > stadistics, but a Map-Administrator is responsible for updating new > elements > on maps, or modifying attributes. _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer