[AccessD] Read-Only error message opening database

Strange, 

I was just gooing to ask a simular question.
I wanted to know if I can trap this error?

I run an MDB (must be an MDB because I change programaticaly some report
properties) every 5 minutes (24x7) with the task scheduler. I find this
technique more stable than leaving the MDB 24x7 open.
Sometimes when the file is backupped or copied at the same moment I get
this read-only message.
The whole folder is backupped about 6 times a day so I do have this
regulary.

But this stays on my server until I click on it. Thus preventing to run
the app next time.

Can I trap this error and just exit if read-only?

Erwin



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Thursday, November 06, 2003 10:09 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Read-Only error message opening database


Hi Terry - and welcome to the list!

Adding to the comments of Charlotte and John, I find it strange that you
didn't receive this message when opening the Access 97 database - unless
you ran that as a runtime? If so that should work for Access 2000 as
well. And, as Charlotte states, the changes that will not be save are
design changes not the data.

Another option could be to convert the database to an mde but other
listers may chime in here as I have never had the need for an mde
running other than for some tests.

/gustav


> I have just found this list so apologies if this question has been 
> asked before (couldn't see it in the archives).

> We have a database that is stored on a shared network drive with the 
> data
> itself in an SQL Server backend.  For security reasons the majority of
users 
> have read-only access to the network drive where the database is
stored.  With 
> Access 97 this worked fine but the database has recently been upgraded
to 
> Access 2000 and now the users receive a message when they open the
database 
> stating that it is read-only so they won't be able to save their
changes (which 
> is incorrect as, of course, the updates are done on the SQL server
which they 
> do have write access to).  Not a major problem but very annoying and
confusing 
> for the users.

> Does anyone know how to disable this error message under Access 2000?

> Thanks,
> Terry Bradford
> (Canberra, Australia)

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com