[AccessD] Read-Only error message opening database

Hi Erwin

OK, but again, a write protected (during backup) backend should not
cause a popup in the fronted (except if you try to write to it, of
course), and why take backup of the frontend all day - you would be
better off creating a working copy of it from a master file when
launching. 

/gustav


> The frontend runs every 5 minutes, I may quit inmediatly in this case
> and do his thing the next time....


> This frontend is in the same folder as the data and runs on the server.
> I supose I could split them up, but I need fast recovery times. So
> that's why I like to keep them togheter.
> This application has 4 front-ends and 2 backends.
> 3 front-ends run on the server, 1 on the client pc's (local copy).
> 1x Front-end is an intermidiate db for ASP/internet access.
> 1x front-end collects E-mails, Faxes and FTP files on the server (checks
> every 5 minutes)
> 1x front-end generates Excel files and faxes a reports whenever asked by
> ASP client or by internal client (checks every other 5 minutes).

> Its the last two from which I Notice my problem.
> Sometimes if I make a minor adjustment to the backend database and the
> front-end (timer is up) runs, I have the same problem. 

> So I tought to catch the error when opening and if the database is in a
> non-editable state to quit inmedatly and try again for next scheduled
> run.

> Erwin



> -----Oorspronkelijk bericht-----
> Van: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] Namens Gustav Brock
> Verzonden: donderdag 6 november 2003 11:03
> Aan: Access Developers discussion and problem solving
> Onderwerp: Re: [AccessD] Read-Only error message opening database


> 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.