Hi folks,
I'd like to understand what causes errors when multiple users simultanously access an unsplit database.
Is it just that the database file is accessed or when changing records?
I want to make an db and keep it unsplit for now during the design stage. However I also would prefer to store it on the company shared folder for back-up purposes, but I wouldnt be able to stop nosey-nellies opening it while I have it open.
I was thinking....
> Open db and show a switchboard.
> On load of switchboard, check if 'dbopened.txt' file exists in db directory.
> - If yes, show msgbox then close db
> - If no, create (empty) file 'dbopened.txt'
> On application close, delete 'dbopened.txt' file.
Im thinking that because the user only gets to a switchboard-style form and doesnt access any actual records, the db is fairly safe from corruption?
Thanks
I'd like to understand what causes errors when multiple users simultanously access an unsplit database.
Is it just that the database file is accessed or when changing records?
I want to make an db and keep it unsplit for now during the design stage. However I also would prefer to store it on the company shared folder for back-up purposes, but I wouldnt be able to stop nosey-nellies opening it while I have it open.
I was thinking....
> Open db and show a switchboard.
> On load of switchboard, check if 'dbopened.txt' file exists in db directory.
> - If yes, show msgbox then close db
> - If no, create (empty) file 'dbopened.txt'
> On application close, delete 'dbopened.txt' file.
Im thinking that because the user only gets to a switchboard-style form and doesnt access any actual records, the db is fairly safe from corruption?
Thanks