Why is my querydef read-only?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just released an MDB to 2 colleagues for testing. It worked fine on one's
machine, but on the other's we got error 3027:

"Cannot update. Database or object is read-only."

The offending line of code assigns a SELECT statement to the SQL property of
a QueryDef object.

All 3 of us are using Office Access 2003 SP2 on Windows XP Pro SP2. The PC
that throws the error has macro security set to Medium, same as mine.

Thanks for any suggestions!
 
because 2 people can't change the same query at the same time.. and if
someone has the application OPEN then you cannot do this.. (using MDB)

of course-- if you just used ADP you would NEVER have this same problem

and more importantly-- you wouldn't have to deal with Sql Passthroughs;
because you could just use parameters in SQL like you should be able to
 
Does each colleague have a separate copy of the database?

Is the database split into a front-end/back-end configuration?

Is the database installed in a directory where the user has full permissions
(read/write/delete)?

If you look in the directory is there a 1 K lock file (.ldb) with the same
name as the database? If you close the database does the lock file get
deleted automatically? If not, can you delete the lock file when the
database is closed?

--
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
..
 
Thanks, Tom!
because 2 people can't change the same query at the same time.. and if
someone has the application OPEN then you cannot do this.. (using MDB)
Click to expand...

Not relevant, actually: I forgot to mention that the installations are
completely local, so there could have been no conflict.
of course-- if you just used ADP you would NEVER have this same problem
Click to expand...

Okay, but then I would have the problem of dealing with an IT department
that would take 3 months to do an impact study before agreeing to consider
committing to planning for the deployment. I'm starting small, by necessity.
and more importantly-- you wouldn't have to deal with Sql Passthroughs;
because you could just use parameters in SQL like you should be able to
Click to expand...

Not quite sure what you mean.
 
Thanks, John!

The answers to your 1st 2 questions are: (1) Yes; (2) No.
I was just about to investigate your remaining questions on the colleagues
PC, when I discovered the problem: he had run the MDB app by double-clicking
on the zipped e-mail attachment, from within Outlook. I'm surprised he got as
far as he did!

Thanks anyway. I'll file your reply for future reference, as I'm sure I
haven't seen the end of deployment problems.
 
Back
Top