Access rights aren't built into DaDaBIK so you would have to arrange something to take care of that on your own. Actually, I'm working on something like that now, as time permits. Basically I installed the DaDaBIK files several times in parallel, with each install targetting the same database table, but having its own unique internal table so it can be configured appropriately.
One install provides an "applicant" view, which allows inserts but no searches, updates or deletes. Another install is for "members" so they can search all records, but not change anything. Another install is for "self-updates" that allows no inserts or deletes but does allow editing. (But the intent here is to restrict the query to the logged-in user. This is what I'm now working on.) And finally there is an "admin" install that allows full access to all records and all DaDaBIK functions.
This is a rather high-overhead solution, but does work with the DaDaBIK files essentially intact. I've incorporated a user authentication script (phpSecureAdmin) that enables all pages to screen for user rights. This can be used to deny access to inappropriate DaDaBIK index and form pages. It also creates a variable that I'm hoping I can use to limit the query for self-updates.
This is all still in progress; I'll post again when it's completed in case anyone else wants to go down the same winding road.
-- Gary
