auto write for read only users

[Laertes]

Hi,

I have created a DB and I want to set up a few read-only users. The
problem is that I have a few "automated" insert/delete procedures.
E.g. when the user logs in his name is recorded on a table. I can
solve this problem by granitng insert access only for the specific
table. That would be ok for this problem, but not for the one
described below....

Moreover, when you load the main data Form it automatically creates a
number of records (specified by the date). When you unload it it
deletes all the empty records. This means that either read-only users
can't access the main data Form or theat they will have insert/delete
access...

Any ideas?

thank you in advance!

Laertes

[Wayne Morgan]

If you are using update or append queries to make your automated entries,
you can specify User's or Owner's permissions for the queries. This is one
of the query properties. If you are using stored queries, right click the
background where the tables are in the query design grid and choose
Properties.

--
Wayne Morgan
Microsoft Access MVP
"Laertes" <bi******@btopenworld.com> wrote in message
news:b2**************************@posting.google.c om...

Hi,

I have created a DB and I want to set up a few read-only users. The
problem is that I have a few "automated" insert/delete procedures.
E.g. when the user logs in his name is recorded on a table. I can
solve this problem by granitng insert access only for the specific
table. That would be ok for this problem, but not for the one
described below....

Moreover, when you load the main data Form it automatically creates a
number of records (specified by the date). When you unload it it
deletes all the empty records. This means that either read-only users
can't access the main data Form or theat they will have insert/delete
access...

Any ideas?

thank you in advance!

Laertes

[Laertes]

I'm actually doing it by code... like this :

......

Set rst = dbs.OpenRecordset("SELECT [date], " _
& "Count([date]) As m FROM Selectron " _
& "GROUP BY [date] HAVING [date] = #" &
Format(a, "mm\/dd\/yyyy") & "#;")
if rst!m = 1 Then
DoCmd.GoToRecord , , acNewRec
Forms![Selectron]![Date].Value = a

......

I tried adding WITH OWNERACCESS OPTION at the end of the recordset,
but still it doesn't like it...

thnx!

Laertes

[Wayne Morgan]

I don't follow where you tried to add the Owner Access option. Try adding it
here:

Set rst = dbs.OpenRecordset("SELECT [date], " _
& "Count([date]) As m FROM Selectron " _
& "GROUP BY [date] HAVING [date] = #" & _
Format(a, "mm\/dd\/yyyy") & "# WITH OWNERACCESS
OPTION;")

--
Wayne Morgan
MS Access MVP
"Laertes" <bi******@btopenworld.com> wrote in message
news:b2**************************@posting.google.c om...

I'm actually doing it by code... like this :

.....

Set rst = dbs.OpenRecordset("SELECT [date], " _
& "Count([date]) As m FROM Selectron " _
& "GROUP BY [date] HAVING [date] = #" &
Format(a, "mm\/dd\/yyyy") & "#;")
if rst!m = 1 Then
DoCmd.GoToRecord , , acNewRec
Forms![Selectron]![Date].Value = a

.....

I tried adding WITH OWNERACCESS OPTION at the end of the recordset,
but still it doesn't like it...

thnx!

Laertes

[Joan Wild]

Wayne Morgan wrote:

I don't follow where you tried to add the Owner Access option. Try
adding it here:

Set rst = dbs.OpenRecordset("SELECT [date], " _
& "Count([date]) As m FROM Selectron " _
& "GROUP BY [date] HAVING [date] = #" & _
Format(a, "mm\/dd\/yyyy") & "# WITH
OWNERACCESS OPTION;")

That won't work, since the 'owner' of this sql statement is the user that's
running this code. An alternative is to create a saved RWOP query based on
Selectron and then write the select statement against that.

--
Joan Wild
Microsoft Access MVP

[Wayne Morgan]

Thanks, Joan.

That makes sense.

--
Wayne Morgan
MS Access MVP
"Joan Wild" <jw***@nospamtyenet.com> wrote in message
news:10*************@corp.supernews.com...

That won't work, since the 'owner' of this sql statement is the user that's running this code. An alternative is to create a saved RWOP query based on Selectron and then write the select statement against that.

--
Joan Wild
Microsoft Access MVP