Gustav Brock
gustav at cactus.dk
Thu Nov 6 04:03:11 CST 2003
Hi Erwin But if you need to make design changes, how would you do that when the file is read-only? And why do you need to backup the frontend six times a day? /gustav > 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.