Hollis,Virginia
HollisVJ at pgdp.usec.com
Wed Mar 19 06:11:00 CST 2003
The databases are in the same folder on the same drive, they have the same startup properties. When I bypass the startup properties, I can delete the record. I have the AllowBuiltinToolbars = False & AllowFullMenus = False. I thought this was the problem so I changed them to True, no luck there. What else should I be looking for? I can't understand why the same code, etc would be so different in 2 separate databases that are basically the same. Virginia -----Original Message----- From: John Frederick [mailto:j.frederick at att.net] Sent: Tuesday, March 18, 2003 3:20 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Can't Delete on Network Drive If you have two mdbs on the same machine that behave differently, look at their security settings. Point to the folder, right click, select the security tab. Something must be different at the folder level. Even if you can't change it, you might be able to tell IT what is needed. -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Hollis,Virginia Sent: Tuesday, March 18, 2003 3:16 PM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Can't Delete on Network Drive I do not understand why it works (can delete) in one database & not another. They are both on the same drive. I do not use the built-in Access security. I am not able to change the security settings for the folder - that is done through IT. So nothing has changed lately. It just has be so puzzled that it works on one database & not the other??? Virginia -----Original Message----- From: John Frederick [mailto:j.frederick at att.net] Sent: Tuesday, March 18, 2003 1:38 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Can't Delete on Network Drive Sounds like OS security. When I gen a system for my home network, I go around and disable all the security gotchas that I know of. If you're on your work network, you want to be more careful. In your case, the os on the machine with the Access data mdb has to either allow anyone coming in from the network to make changes or it has to have a login/password for the client and you have to either supply it when accessing the data mdb or build it into your links and OpenRecordset commands. If you don't care about security, I suggest the following: 1. On the data machine, enable the guest account. How you do that is os dependent. On W2k, go to Control Panel/Administrative Tools/Computer Management/Local Users and Groups. Select User: "Guest", click "Account is Disabled" off, and for good measure, add the Guest and Everyone to the Administrators Group. 2. On the folder containing the data mdb, right click, choose security, and give everyone listed full permissions for the folder. 3. Either wait a day to give someone who knows more about security to advise you not to do this, OR, take careful notes so you can undo it. -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Hollis,Virginia Sent: Tuesday, March 18, 2003 1:34 PM To: accessd at databaseadvisors.com Subject: [AccessD] Can't Delete on Network Drive I need to delete a record using a form (this is 97). The strange thing is if I copy the database to my hard drive I can delete the record, but when the database is on the network drive (where it lives) I get the error message "2046, The Command or Action DeleteRecord is not Available Now". I use the same code in another database on the same network drive and folder & it works fine - I can delete the record. I tried copying the database to my hard drive & copying it back to the network. I even imported everything into a new database. What should I be looking for in this database that would prevent deletions just because it is on the network drive? On the command button I have: Me.AllowDeletions = True RunCommand acCmdDeleteRecord Virginia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030319/8b048a0e/attachment-0001.html>