using an on-the-fly query in a read-only database

[Katherine Hanson]

I have an Access database in a network folder that only a few users
have write access to. I'd like other users to be able to query the
database but not update records. The problem is the code I'm using in
my main search form:

CurrentDb.QueryDefs("qryPubs").SQL = strSQL
RefreshDatabaseWindow
Me.RecordSource = "qryPubs"

When a user without write access to the folder tries to open the form,
they get run-time error 3027 (Cannot update. Database or object is
read-only.) I'd rather not have to move my database out to a public
folder. Is there another way to set my form's record source to an
on-the-fly query?

TIA.

Katherine

[pietlinden]

split front end from back, relink, and distribute the front end to the
users. Then they can modify the FE all they want.

[MacDermott]

Skip the QueryDef.
Just use this:
Me.RecordSource=strSQL

"Katherine Hanson" <er***************@gmail.com> wrote in message
news:11**********************@l41g2000cwc.googlegr oups.com...

I have an Access database in a network folder that only a few users
have write access to. I'd like other users to be able to query the
database but not update records. The problem is the code I'm using in
my main search form:

CurrentDb.QueryDefs("qryPubs").SQL = strSQL
RefreshDatabaseWindow
Me.RecordSource = "qryPubs"

When a user without write access to the folder tries to open the form,
they get run-time error 3027 (Cannot update. Database or object is
read-only.) I'd rather not have to move my database out to a public
folder. Is there another way to set my form's record source to an
on-the-fly query?

TIA.

Katherine

[King Ron]

Ola K:
Actually the problem is not so much your query, but the fact that
anytime an Access database is opened, a locking database (.ldb) is
created to manage.record locks. If the logging on user does not have
Operating System write rights, the db open fails with that error.

Since the problem is the OS and not Access, there's really nothing you
can do but work around the rights issue. Possibly you could create a
separate folder for this application and give all of your users write
access to it, or create a dummy user that only has access to that
single folder. Alternatively, you could webify the query and connect
thru IIS <== (another whole rights issue!).

I'm out of ideas...

rock and roll
King Ron of Chi

[Katherine Hanson]

MacDermott wrote:

Skip the QueryDef.
Just use this:
Me.RecordSource=strSQL

Perfect! Thanks so much for your help, everyone.

Katherine