At 05:19 AM 12/02/2005 +0000, you wrote:

> > ..
> > if not IdiotProtect then
> > begin
> > // proceed to apply strings to the XXXSQL properties, or to set
> > RequestLive true
> > end
> >
>Do you mean to say that I have to customize the xxxsql properties for
>every role?

Only if your privileges logic is that complicated. I don't think you are
following the logic here.

>If that's what iam going to do I think there no need to
>set the priviledge on the server side. My problem is that when a user
>without a insert priviledge by just opening the dataset produce an
>error because of the preparing of the xxxsql properties set.

You don't "customise the xxxxsql properties for every role". At login, you
decide whether the current user/role combination is IdiotUser or not, and
set that property.

For each dataset, you will have two possible conditions: updatable or not
updatable. For the datasets where differences in user privileges have to
be taken account of, you only have to refer to the "IdiotUser" property
(call it whatever you like!!) Go back to the previous posting and think
about the logic.

>But I
>understand that I won't allow him to insert when he tries to. So I
>wish to avoid the preparing of the xxxsql properties.

Exactly.

Helen