In Reply To:
I'm not sure I do understand... You can always "hide" links in templates, but that is only really a workable solution if you're positive that the script will only be used by benevolent, luddite users. A user who wanted to mess with your tables and had any familiarity with the script could always pass the information in the url directly - as in: http://www.yoursite.com/cgi-bin/ db.cgi?db=xxx&do=modify_form. Probably not the best idea.
Right! I wanted to solve that problem by using plugins.
In Reply To:
Where I get confused is when you start talking about pre-add and pre-modify plugins... I don't know what you mean by that or what it would be intended to accomplish.
I have never written GT prugins before, so I am not sure where I am talking about.
I got my info from the help pages of Links SQL on plugins. It is explained there that plugins are called before and after certain GT actions (like adding, deleting and modifying records). In these plugins, you can specify whether the action itself should be executed or not. So my idea was, to check in the plugin if the current user has the right to do the requested action on the specified table.
I am not sure if this is more clear than my previous posting....
Jasper
http://www.bookings.org