| Thread | Last Post | Replies |
|
| default "read only" | 30 Apr 2004 22:12 GMT | 2 |
I want to burn my Access 2002 (Windows XP Professional) files onto a CD and use them on my office computer which has the same version of Access. The files are all "read only". I tried unchecking the read only box when I had
|
| Who's in my database? | 30 Apr 2004 19:40 GMT | 1 |
I want to create a function that will allow me to see who is in a shared database at any given time. I've read and copied the code from the KB Article: "HOW TO: Check Who Logged into Database with Jet
|
| Securing Admin User | 30 Apr 2004 18:56 GMT | 2 |
H I created an Access Workgroup file then created a new database having joined the workgroup. In the Security option I then created a user Manager and made it a member of Admins. I then removed Admin from Admins and made sure that all permissions were removed from User group and ...
|
| Modules | 30 Apr 2004 11:26 GMT | 1 |
How do I secure my modules. I do not see a listing for this in permissions? thanks
|
| unable to copy a database | 30 Apr 2004 03:39 GMT | 1 |
I am unable to copy my database to another computer on my network. When I try to open it on another computer, I either get the message that it can't find the file (I can see it in Explorer, so I know it's there) or that I don't
|
| Could not Lock File error | 30 Apr 2004 03:23 GMT | 2 |
I'm trying to share an access database with an entire workgroup. I copied the database to the file server and assigned permissions. I set up the person responsible for modifying this file with FULL PERMISSION on the parent
|
| Compacting secure database | 30 Apr 2004 03:00 GMT | 8 |
In my VB app I give the user the option to compact a database. The statement is Set mDBEngine = New JRO.JetEngine mDBEngine.CompactDatabase myDBConStr, newDBConStr
|
| access | 30 Apr 2004 00:49 GMT | 2 |
I create a database (table, form..) and set security for user. I save it locally and test the security permition it seems ok. I copy the data file to network and open it from network. When I open it which no longer ask for user
|
| linking to a secured database | 29 Apr 2004 23:28 GMT | 3 |
I have a few databases which need to link to a few tables within a secured database. I have set the permissions of the secured database to allow the required rights however, I am unable to link the tables. Any suggestions as to what I should do or where I can go to find this ...
|
| I can't access secure web sites | 29 Apr 2004 20:03 GMT | 2 |
I can go to just about any web page except ones where I have to enter personal data, i.e. credit card number. I can shop and place items in my cart, but, when I click on "Check Out" and I get a "Page can not be displayed" message. Help, help, help!!!
|
| AllowBypassKey setting on MDE file | 29 Apr 2004 14:49 GMT | 4 |
I currently have a 'front end' .mdb file which has table links to the back end. Each time I change a form, for example, I create a new .mde file which I distribute to the users. I'd like to prevent users using the shift key
|
| Security in general | 29 Apr 2004 10:31 GMT | 7 |
Hi. I've not done any work on securing my dbs (Access 2003) and I've read enough on this newsgroup to know that its not without its frustrations. Is there another simpler way? I currently have just one general password
|
| error!!! Operation must use an updateable query. | 29 Apr 2004 04:20 GMT | 2 |
[Microsoft][ODBC Microsoft Access Driver] Operation must use an updateable query. Why do i get the message above? The system is Windows 2003 server IIS6 I am sure there is read/write permissions for Internet Guest Account user
|
| Disable Shift-Key in .ADP/.ADE (2002-2003) | 29 Apr 2004 01:06 GMT | 1 |
Hello friends, I need to prevent users to bypass start-up options when opening my MS Access project file, in an .ade version I found various codes for setting "AllowBypasskey" to false, but the codes that are shared out there, work for .mdb... All methods that I have used so far-- ...
|
| Sharing with Access 2003 | 28 Apr 2004 22:46 GMT | 2 |
I have a split database (front end and back end) built in Access 2002. It has been shared among several Access 2002 users for months with no conflicts. We recently purchased a workstation with Access 2003 and when he
|