Disk Error "kcdBCreator" <kayz_creation[ at ]cox.net> 08.06.2006 23:16:03 A client wanted to place an MS Access 2000 database in a folder on her C: drive and then share the folder on her c: drive out to certain users using a local network setup. Those certain users all have Full Control (through the shared folder). However, if more than one person attempts to add new data to the table or to access two different forms, the second person gets a DISK ERROR message and then the entire MS Access database locks up with a message 'cannot execute command' if the user attempts to click on any button in the main menu. The only way to remove this message is for the user to exit out of the dB and close the shared folder. The MS Access database and all forms have been set to only lock edited records and the dB has been split with the front-end residing on the different workstations while the back-end resides on the clients shared drive. The front-end tables have all been linked through the link manager utility as well. My question is why is the DISK ERROR occurring? Would this still occur if instead of using the client's c: drive as a network server, the client moves the database to a true server?

Re: Disk Error "kcdBCreator" <kayz_creation[ at ]cox.net> 09.06.2006 18:04:44 Can someone please help me with this? I have checked all of the folder settings and the users all have full control and can enter the database at the same time but if they try to enter data or even view data from the same table at the same time, the DISK ERROR message results. Please, help with this from an Access pro would be much appreciated... kcdBCreator wrote: [Quoted Text] > A client wanted to place an MS Access 2000 database in a folder on her > C: drive and then share the folder on her c: drive out to certain users > > using a local network setup. Those certain users all have Full Control > > (through the shared folder). However, if more than one person attempts > > to add new data to the table or to access two different forms, the > second person gets a DISK ERROR message and then the entire MS Access > database locks up with a message 'cannot execute command' if the user > attempts to click on any button in the main menu. The only way to > remove this message is for the user to exit out of the dB and close the > > shared folder. The MS Access database and all forms have been set to > only lock edited records and the dB has been split with the front-end > residing on the different workstations while the back-end resides on > the clients shared drive. The front-end tables have all been linked > through the link manager utility as well. My question is why is the > DISK ERROR occurring? Would this still occur if instead of using the > client's c: drive as a network server, the client moves the database to > a true server?

Re: Disk Error "Larry Linson" <bouncer[ at ]localhost.not> 11.06.2006 00:39:50 I'm not sure what "Full Control" means. Do the users have create file and and delete file rights? Problems not occurring with a single user, but with the second and following concurrent user, do happen when they don't have file create/delete rights. But, even that should not, I think, give the kind of error that you describe. Aside from the possibility of a problem with installing Access (which doesn't seem likely unless all were installed from a defective file/CD), or some wierd type of database corruption, I don't have any other suggestions. Larry Linson Microsoft Access MVP "kcdBCreator" <kayz_creation[ at ]cox.net> wrote in message news:1149876284.593463.189990[ at ]i39g2000cwa.googlegroups.com... [Quoted Text] > Can someone please help me with this? I have checked all of the folder > settings and the users all have full control and can enter the database > at the same time but if they try to enter data or even view data from > the same table at the same time, the DISK ERROR message results. > Please, help with this from an Access pro would be much appreciated... > > > kcdBCreator wrote: >> A client wanted to place an MS Access 2000 database in a folder on her >> C: drive and then share the folder on her c: drive out to certain users >> >> using a local network setup. Those certain users all have Full Control >> >> (through the shared folder). However, if more than one person attempts >> >> to add new data to the table or to access two different forms, the >> second person gets a DISK ERROR message and then the entire MS Access >> database locks up with a message 'cannot execute command' if the user >> attempts to click on any button in the main menu. The only way to >> remove this message is for the user to exit out of the dB and close the >> >> shared folder. The MS Access database and all forms have been set to >> only lock edited records and the dB has been split with the front-end >> residing on the different workstations while the back-end resides on >> the clients shared drive. The front-end tables have all been linked >> through the link manager utility as well. My question is why is the >> DISK ERROR occurring? Would this still occur if instead of using the >> client's c: drive as a network server, the client moves the database to >> a true server? >

Re: Disk Error "kcdBCreator" <kayz_creation[ at ]cox.net> 12.06.2006 23:16:50 Hi Larry, Thanks for your reply. Yes, all users have create and delete file rights. User Groups were not created in Access to limit rights. Do you think this is the problem? Should I create usergroups to eliminate the Disk or network Error Message? Thanks again for your help! Larry Linson wrote: [Quoted Text] > I'm not sure what "Full Control" means. Do the users have create file and > and delete file rights? Problems not occurring with a single user, but with > the second and following concurrent user, do happen when they don't have > file create/delete rights. > > But, even that should not, I think, give the kind of error that you > describe. > > Aside from the possibility of a problem with installing Access (which > doesn't seem likely unless all were installed from a defective file/CD), or > some wierd type of database corruption, I don't have any other suggestions. > > Larry Linson > Microsoft Access MVP > > "kcdBCreator" <kayz_creation[ at ]cox.net> wrote in message > news:1149876284.593463.189990[ at ]i39g2000cwa.googlegroups.com... > > Can someone please help me with this? I have checked all of the folder > > settings and the users all have full control and can enter the database > > at the same time but if they try to enter data or even view data from > > the same table at the same time, the DISK ERROR message results. > > Please, help with this from an Access pro would be much appreciated... > > > > > > kcdBCreator wrote: > >> A client wanted to place an MS Access 2000 database in a folder on her > >> C: drive and then share the folder on her c: drive out to certain users > >> > >> using a local network setup. Those certain users all have Full Control > >> > >> (through the shared folder). However, if more than one person attempts > >> > >> to add new data to the table or to access two different forms, the > >> second person gets a DISK ERROR message and then the entire MS Access > >> database locks up with a message 'cannot execute command' if the user > >> attempts to click on any button in the main menu. The only way to > >> remove this message is for the user to exit out of the dB and close the > >> > >> shared folder. The MS Access database and all forms have been set to > >> only lock edited records and the dB has been split with the front-end > >> residing on the different workstations while the back-end resides on > >> the clients shared drive. The front-end tables have all been linked > >> through the link manager utility as well. My question is why is the > >> DISK ERROR occurring? Would this still occur if instead of using the > >> client's c: drive as a network server, the client moves the database to > >> a true server? > >

Re: Disk Error "Larry Linson" <bouncer[ at ]localhost.not> 13.06.2006 02:00:57 If by "usergroups," you mean Access User/Group Level Security, no, I wasn't talking about that at all. I was talking about user's Windows rights of access to the shared folder. If the last user to close the database does not have delete file authority, the ..LDB file can't be deleted, and that can leave an LDB open and 'mislead' Access. Larry Linson Microsoft Access MVP "kcdBCreator" <kayz_creation[ at ]cox.net> wrote in message news:1150154210.068028.94890[ at ]f14g2000cwb.googlegroups.com... [Quoted Text] > Hi Larry, > > Thanks for your reply. Yes, all users have create and delete file > rights. User Groups were not created in Access to limit rights. Do > you think this is the problem? Should I create usergroups to eliminate > the Disk or network Error Message? > > Thanks again for your help! > > > Larry Linson wrote: >> I'm not sure what "Full Control" means. Do the users have create file and >> and delete file rights? Problems not occurring with a single user, but >> with >> the second and following concurrent user, do happen when they don't have >> file create/delete rights. >> >> But, even that should not, I think, give the kind of error that you >> describe. >> >> Aside from the possibility of a problem with installing Access (which >> doesn't seem likely unless all were installed from a defective file/CD), >> or >> some wierd type of database corruption, I don't have any other >> suggestions. >> >> Larry Linson >> Microsoft Access MVP >> >> "kcdBCreator" <kayz_creation[ at ]cox.net> wrote in message >> news:1149876284.593463.189990[ at ]i39g2000cwa.googlegroups.com... >> > Can someone please help me with this? I have checked all of the folder >> > settings and the users all have full control and can enter the database >> > at the same time but if they try to enter data or even view data from >> > the same table at the same time, the DISK ERROR message results. >> > Please, help with this from an Access pro would be much appreciated... >> > >> > >> > kcdBCreator wrote: >> >> A client wanted to place an MS Access 2000 database in a folder on her >> >> C: drive and then share the folder on her c: drive out to certain >> >> users >> >> >> >> using a local network setup. Those certain users all have Full >> >> Control >> >> >> >> (through the shared folder). However, if more than one person >> >> attempts >> >> >> >> to add new data to the table or to access two different forms, the >> >> second person gets a DISK ERROR message and then the entire MS Access >> >> database locks up with a message 'cannot execute command' if the user >> >> attempts to click on any button in the main menu. The only way to >> >> remove this message is for the user to exit out of the dB and close >> >> the >> >> >> >> shared folder. The MS Access database and all forms have been set to >> >> only lock edited records and the dB has been split with the front-end >> >> residing on the different workstations while the back-end resides on >> >> the clients shared drive. The front-end tables have all been linked >> >> through the link manager utility as well. My question is why is the >> >> DISK ERROR occurring? Would this still occur if instead of using the >> >> client's c: drive as a network server, the client moves the database >> >> to >> >> a true server? >> > >

Re: Disk Error "kcdBCreator" <kayz_creation[ at ]cox.net> 13.06.2006 19:06:30 Hi Larry, If the dB were built in Access 2002 and the client has Microsoft Office 2003 Pro, will this cause the 'disk or network error' message? Larry Linson wrote: [Quoted Text] > If by "usergroups," you mean Access User/Group Level Security, no, I wasn't > talking about that at all. > > I was talking about user's Windows rights of access to the shared folder. If > the last user to close the database does not have delete file authority, the > .LDB file can't be deleted, and that can leave an LDB open and 'mislead' > Access. > > Larry Linson > Microsoft Access MVP > > > "kcdBCreator" wrote in message > news:1150154210.068028.94890[ at ]f14g2000cwb.googlegroups.com... > > Hi Larry, > > > > Thanks for your reply. Yes, all users have create and delete file > > rights. User Groups were not created in Access to limit rights. Do > > you think this is the problem? Should I create usergroups to eliminate > > the Disk or network Error Message? > > > > Thanks again for your help! > > > > > > Larry Linson wrote: > >> I'm not sure what "Full Control" means. Do the users have create file and > >> and delete file rights? Problems not occurring with a single user, but > >> with > >> the second and following concurrent user, do happen when they don't have > >> file create/delete rights. > >> > >> But, even that should not, I think, give the kind of error that you > >> describe. > >> > >> Aside from the possibility of a problem with installing Access (which > >> doesn't seem likely unless all were installed from a defective file/CD), > >> or > >> some wierd type of database corruption, I don't have any other > >> suggestions. > >> > >> Larry Linson > >> Microsoft Access MVP > >> > >> "kcdBCreator" wrote in message > >> news:1149876284.593463.189990[ at ]i39g2000cwa.googlegroups.com... > >> > Can someone please help me with this? I have checked all of the folder > >> > settings and the users all have full control and can enter the database > >> > at the same time but if they try to enter data or even view data from > >> > the same table at the same time, the DISK ERROR message results. > >> > Please, help with this from an Access pro would be much appreciated... > >> > > >> > > >> > kcdBCreator wrote: > >> >> A client wanted to place an MS Access 2000 database in a folder on her > >> >> C: drive and then share the folder on her c: drive out to certain > >> >> users > >> >> > >> >> using a local network setup. Those certain users all have Full > >> >> Control > >> >> > >> >> (through the shared folder). However, if more than one person > >> >> attempts > >> >> > >> >> to add new data to the table or to access two different forms, the > >> >> second person gets a DISK ERROR message and then the entire MS Access > >> >> database locks up with a message 'cannot execute command' if the user > >> >> attempts to click on any button in the main menu. The only way to > >> >> remove this message is for the user to exit out of the dB and close > >> >> the > >> >> > >> >> shared folder. The MS Access database and all forms have been set to > >> >> only lock edited records and the dB has been split with the front-end > >> >> residing on the different workstations while the back-end resides on > >> >> the clients shared drive. The front-end tables have all been linked > >> >> through the link manager utility as well. My question is why is the > >> >> DISK ERROR occurring? Would this still occur if instead of using the > >> >> client's c: drive as a network server, the client moves the database > >> >> to > >> >> a true server? > >> > > >

Re: Disk Error "Larry Linson" <bouncer[ at ]localhost.not> 15.06.2006 04:25:07 "kcdBCreator" wrote > If the dB were built in Access 2002 and > the client has Microsoft Office 2003 Pro, > will this cause the 'disk or network error' > message? It shouldn't. Access 2002 and 2003 share the same database file format, but both create databases by default in Access 2000 file format. In any case, no, none of these should cause the problem. Because I need to test DBs in various versions, I have both A2002 and A2003, generating in 2002/2003 database file format, and I switch DBs between them "at will" without any problems. MVP Tony Toews has told you that it is most likely indicative of a hardware or connection error, and he's done more with this kind of error than I have. Larry Linson Microsoft Access MVP

Re: Disk Error "Maria Hermann" <mariasideas[ at ]olypen.com> 19.06.2006 05:30:37 ---------- In article <1150154210.068028.94890[ at ]f14g2000cwb.googlegroups.com>, "kcdBCreator" <kayz_creation[ at ]cox.net> wrote: [Quoted Text] > > Hi Larry, > > Thanks for your reply. Yes, all users have create and delete file > rights. User Groups were not created in Access to limit rights. Do > you think this is the problem? Should I create usergroups to eliminate > the Disk or network Error Message? > > Thanks again for your help! > > > Larry Linson wrote: >> I'm not sure what "Full Control" means. Do the users have create file and >> and delete file rights? Problems not occurring with a single user, but with >> the second and following concurrent user, do happen when they don't have >> file create/delete rights. >> >> But, even that should not, I think, give the kind of error that you >> describe. >> >> Aside from the possibility of a problem with installing Access (which >> doesn't seem likely unless all were installed from a defective file/CD), or >> some wierd type of database corruption, I don't have any other suggestions. >> >> Larry Linson >> Microsoft Access MVP >> >> "kcdBCreator" <kayz_creation[ at ]cox.net> wrote in message >> news:1149876284.593463.189990[ at ]i39g2000cwa.googlegroups.com... >> > Can someone please help me with this? I have checked all of the folder >> > settings and the users all have full control and can enter the database >> > at the same time but if they try to enter data or even view data from >> > the same table at the same time, the DISK ERROR message results. >> > Please, help with this from an Access pro would be much appreciated... >> > >> > >> > kcdBCreator wrote: >> >> A client wanted to place an MS Access 2000 database in a folder on her >> >> C: drive and then share the folder on her c: drive out to certain users >> >> >> >> using a local network setup. Those certain users all have Full Control >> >> >> >> (through the shared folder). However, if more than one person attempts >> >> >> >> to add new data to the table or to access two different forms, the >> >> second person gets a DISK ERROR message and then the entire MS Access >> >> database locks up with a message 'cannot execute command' if the user >> >> attempts to click on any button in the main menu. The only way to >> >> remove this message is for the user to exit out of the dB and close the >> >> >> >> shared folder. The MS Access database and all forms have been set to >> >> only lock edited records and the dB has been split with the front-end >> >> residing on the different workstations while the back-end resides on >> >> the clients shared drive. The front-end tables have all been linked >> >> through the link manager utility as well. My question is why is the >> >> DISK ERROR occurring? Would this still occur if instead of using the >> >> client's c: drive as a network server, the client moves the database to >> >> a true server? >> > >