Hi Tom, You've raised an interesting point: the difference between being connected in Read Only mode and in Multi User mode.
If I connect to a multi-user database using "connect db read" I would _assume_ that the db is updateable by others but not by me. Equally, if I connect to a single-user db in the same way then I can't update the database (and nobody else can connect to it). On the basis that backups should be done in single-user mode - as you correctly point out - then read only should be superfluous... Being paranoid about my data any action that can be taken to reduce the risk of corruption for any reason seems worthwhile and next to not having the files open (or the PC switched off, I guess) then read-only mode should be best. As many others have noted here, users tend to leave DBs connected while they have lunch, got home for the night, or the week end, or on holiday, whatever - I know, I've been one!!! In this case I have been writing apps that look up data and using the db in read only mode as no changes are to be made so it seemed sensible to carry that through wherever possible. Backing up seemed an obvious place as it's the time you most want an uncorrupted copy. The strange thing is that RELOAD works in read-only mode yet BACKUP doesn't seem to - I do both - and AUTOCHK the DBs before and after. (You might gather from all this that I lost some data once. Actually, it was twice - two days running - I had to go cap in hand the second time and I learnt my lesson under a torrent of - probably well-intentioned - but cruel verbal abuse!! I seem to remember that the words "fool" and "idiot" were used <g>.) Nevertheless, if my experiences saves anybody else the same heartache and if anyone at RBTI can explain why this happens - assuming I'm right - then everyone gains. Cheers, Alastair. ----- Original Message ----- From: "Tom Grimshaw" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 15, 2002 5:21 PM Subject: Re: Internal Error on Backup command > G'day Alastair, > > At 18:52 14/02/02 +0000, you wrote: > >I'd like to come back to this problem from November last year. > > > >I've spent the last two days playing around to see if I could resolve it > >and I have! > > > >Actually, I resolved it a while ago by creating a playback file with a > >[Return] in it - but that was not the correct way to do it <g>. > > > >The real solution was that the database was connected as read only and as > >soon as I removed that restriction the problem disappeared. > > Well done on the detective work. > > >The question now is why "CONNECT db READ" should cause the BACKUP command > >to fail? > > Just a couple of guesses, security (if you're only giving them read access, > the ability to do a backup to a text file may have been considered > inappropriate) > and if you are read only then structural changes may be in progress, in which > case a backup in the middle... > > >Anybody got any ideas, please?? I'm trying to write all my code now so > >that the database is open in read/write mode only when it is needed to be so. > > Warmest regards, > > > Tom Grimshaw > coy: Just For You Software > tel: 612 9552 3311 > fax: 612 9566 2164 > mobile: 0414 675 903 > > post: PO Box 470 Glebe NSW 2037 Australia > street: 3/66 Wentworth Park Rd Glebe NSW 2037 > > email: [EMAIL PROTECTED] > web: www.just4usoftware.com.au > > This email and any files transmitted with it are confidential to the > intended recipient and may be privileged. If you have received this email > inadvertently or you are not the intended recipient, you may not > disseminate, distribute, copy or in any way rely on it. Further, you should > notify the sender immediately and delete the email from your computer. > Whilst we have taken precautions to alert us to the presence of computer > viruses, we cannot guarantee that this email and any files transmitted with > it are free from such viruses. > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
