Restricting Users Ability To Read Only Version: 2003
Feb 22, 2006
I have a very simple Access database that contains a form where users enter sheduling information...I wish to limit a group of users to be able to read this information only and not modify or add to it.
The tables are in a back end mdb. The rest is in a front end mdb. And the users actually use the mde file when working with the schedule.
What in your opinion is the least complicated method for providing some users with the ability to add/modify and some with read only.
If i split my Data base into a front and back end how would i restrict certain users only to input data on certain forms. Also how would i prevent them from accessing certain information.
I am receiving an unexpected message when a user tries to launch a form that the user does not have permission for via the Access Security-Permissions setting that I have configured.
I am trying to set my Access db up so that Guest users can only access 2 Forms - the Switchboard and the Main form. There is a Maintenance Form and I don't want Guest users having access to it.
I have configured Security and created a Group named Guestgrp. I have also created a user named Guest that is assigned to the Users and Guestgrp groups.
The Users group is currently set up with NO permission for any form.
Here are the Guestgrp permissions for the forms, db and tables
The following forms have Open/Run and Read Design permission Switchboard MainForm
The following forms have NO Permissions selected Maintenance Form
The database permission is set to Open/Run
Table permissions The Guest group has Read Design and Read Data permission for all tables
so here is what happens............... My Guest user can log in and launch the Switchboard form and can launch the Main Form from the switchboard. BUT...................... When my Guest user clicks on the Switchboard button for the Maintenance Form, the following message pops up: There was an error executing the command.
Is this the normal way for Access to indicate that the user does NOT have permission to access a form? I am guessing/hoping that it isn't and if configured properly there would be a message indicating that permission is denied or something of that nature.
If anyone has any comments, suggestions on the error in my ways, I appreciate any comments/suggestions/clarifications.
My department and limited the users to only specific tables based on their need and role. However, users have expressed the need to view past work. I do not want to give them access to the table - I am thinking that there should be a way to create a report that shows the data, but how would I set up a search filter option so they can find the one record that they are looking for?
I have a timesheet data base and I wanted to find a way to restrict employees from editing other employees timesheets only their own timesheet... .is it possible with access 2010?
Are there any issues with converting an older 97 database to 2003? Is it a straight conversion, or will there be differences that affect the way the database will run if converted? I've read somewhere that it is possible to use the newer version to open the database w/o converting it. It seems silly to have to install 97 on a new computer in order to view the db.
Got a problem here with Access 2003: got 36 categories (example: volume from 0-0.1=category 1 vol from 0.1-0.2=category 2 etc) and a whole bunch of records (in a table) stating volume per record (0.111, 0.23456 etc). For each record I need to know which category it is. Now in order to prevent me from writing 36 update queries for each category (if vol>0 and <0.1 then category = 1 etc) there must b a smarter/faster way to do this. What is it?
I am getting the following error when Synchronizing Now for Replicated database. The total database size is only 22 megs (contains reports and forms). This just started happening recently, otherwise it was fine before. My machine is running WinXP Pro SP2 (with latest service pacs) on an AMD DualCore 3800 with 1gig RAM. Once you hit the OK it continues and competes successfully (at least it look OK). Any ideas what this could be or to eliminate it popping up? I run the database with minimum of programs at the same time.
I have a db with more than 100 forms, reports - objects. My backend tables are linked sybase tables. What is the best way to hand this over to the users?
1. I want to create a mde version (which is not working, here's my problem :mad: Failure In Creating MDE File (http://www.access-programmers.co.uk/forums/showthread.php?t=94465) 2. I want a way to send this application to the user, in order that is installs on their desktop or a location i specify on the user's drive. I have no clue how to accomplish this, but i know that when i download some applications they do end up on my desktop :rolleyes: , so they must have done it somehow. Please help? 3. I want to have a master mdb hidden on the network somewhere, and when i make changes to that (e.g. my form or reports). And the next time the user goes into the version installed on their drive, it checks for the last version of the front end, and if that's not it, it erases the old one they have and installs my new version for them automatically. I know this can be done. Can you help me?
I'd really appreciate if anyone can help me please in any way. Advice, links, tutorial, whatever. Many blessings will come to you!
Ghudson! Before you attack me, i've done a search on the forum and though i've seen some posts, i can't seem to find one best for my means :) Thanks!
Hi, My database consists of some personal data and a photo of each person. I am trying to include these photos when I browse the database via ADP. I have found instructions how to do so at Microsoft website (article ID: 285820) Link for it: http://support.microsoft.com/?kbid=285820 The problem is I cannot make it !!!!!!!! Where exactly should I paste the VBscript in the page code to execute displaying of the photos??????? I am happy to send you the head portion of my page code if anybody knows where to paste it.....
I have developed an application and packed it into a runtime version. However, in the runtime version the shortcut menus do not work. The reason why I want the user to have that possibility is that the application has two hyperlink fields and it is much easier for the users to be able to browse to the documents instead of typing each link with all the errors that might give as well. Any help would be appreciated.
I have been trying to set up a batch file to allow users to copy the latest version of the front end whenever a change is made. The following is the code that I am trying to get to work properly. The first part works fine, the old front end is copied to a folder on the user's desktop as a backup. But I cannot get the copy of the server - the "P" drive, to overwrite the current copy on the user's desktop. Actually I cannot get the code to copy the new front end from the server and install it on the user's desktop. I think the path is correct for I seem to be able to run the new front end from the server.
When I look for the location on my computer, the server locations is listed as:
General (Servernamefiles) (P: ) (there is no space after the P: it seems to result in a smiley face when I type it and try to post it).
for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set year=%%c for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set month=%%a for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set day=%%b set TODAY=%year%-%month%-%day% rem echo %TODAY%
[Code] .....
This code works so I thought that the path was correct rem this works rem start the new DB front end Start P:AccessMainSplitBENewFrontEndDBMain.accdb
But this code does not. echo f | xcopy /f/y/ P:AccessMainSplitBENewFrontEndDBMain.accdb c:UsersUserNameDesktopDBMain.accdb
Neither does this: echo f | xcopy /f/y/ ServerNamefilesP:AccessMainSplitBENewFrontEn dDBMain.accdb c:UsersUserNameDesktopDBMain.accdb
I want to make an Access database of my collection of antique swords that I can put on a CD. This DB would also include as many as 5 digital images for each record.
Some of my friends may not have Access 2007 on their PC. Is there a viewer that I can put on the CD with my database so they can view it without them having to buy the Access program??
I have a Front-End Access Data Project file (ADE compiled format for distribution) that I purposely have the Read-Only file attribute set to True.
I've been using it this way for about 7 years starting with Access 97 and the current version is 2000. I am upgrading the app to 2003 now and everything with the conversion is fine except when I set the Read-Only file attribute to True it all of a sudden when starting it no longer connects to the Back-End (sql server) and displays a "form load cancelled" error before hanging.
If I disable the Read-Only attribute, everything is fine again, but I prefere not to do this because that will require me to rework my auto updater.
I use it this way because it prevents bloating of the file and allows for my auto updater to determine new version by using the file modification date.
Moving to new computer, both under Win XP pro, Access 2003. New computer is MacBook Air running Parallels. Transferred Access database via an external hard drive. Now the data shows up as Read Only. Is there a procedure to run down the cause and make the data accessible?
I have two separate database files, a front end with all my forms and a back end with all my tables. The backend is stored on a network drive, is there any way of being able to store the frontend on the drive with the backend? Users do not use the actual computer to store information or access files, everything is usually saved on the network drive. I have created a shortcut that launches the front end database in the read only kiosk mode.
Our company recently switched over to a Microsoft 2003 server and I noticed in our database, before several employees could work in our access database. Now only 1 person at a time can enter the database. I splited the database and added shortcuts of the front end on each individual's desk but again only 1 person at a time can make entries. We all share a M drive. How do I fix it so we all can work in the database at the same time?
Before the upgrade, we had the 2000 server and everything worked fine w/ the access database; we all could work in the database; however, w/ the new 2003 server we are having problems as I explained above.
I am looking for a little help getting a database created in access 2000 to open in access 2003. The creater of the database put security on it and I have the security doc. However, I do not know how to give permission to open the database in 2003.
I support a database for some users who don't find the built in search function (ctl+f) to be useful enough.
The main data entry form of the database has fields for subdivision, lot number and address, any of which they may use to find the record they want. They're requesting that I add two types for searching: * select sub and/or lot number as search criteria and have the selected record populate the screen * type in a freeform address and have the record populate the screen
I'm debating about what the best approach would be to do this. Should I have a command button which opens a pop up form with the fields? If so, what is the code I will need to take the data selected/entered on the popup, run a query and then populate the underlying form? I think I need to pass parameters but I'm inexperienced at this so I need some guidance.
Also thinking that if I do create a popup form that I'll use it in the open event on the data entry form as well.
I have a database with a huge table on the back-end, and then I want to set up various front-ends that will only show particular records that a user is interested in.
I notice that, when I query the big table without any join, I get all the records and also a space for entering a new record--that's what I want. But, when I add a join that serves to filter the records to the ones the particular user would be interested in, the space for entering a new record goes away. This is the case whether I view the query itself, or the form that uses the query.
Does anyone know how I can keep the ability to add new records while also making the query a bit more complex?
From a Access database that I inherited. Users used to be able (from a form) run a query and then add data (i.e, new rows). But now that the the database is split and the backend is on MS-SQL, they no longer can do this. I do not think this will be possible. I think they will have to add data directly to the table or have another form for adding data.
Selecting the "General" group as this involves SQL Server Stored Procedures (SP) and VBA code and Reports and and and...
Client has requested exception type reporting noting when a price in a Bill of Materials (BOM) changes.
I am thinking to solve this with the following steps:
1) EXEC SP to run "this week's" BOM reports, automated, figure out how to print to PDF or something 2) EXEC SP to run "this week vs last week" exception report. A giant nasty:
Code: SELECT cols.... FROM [xyz] LEFT JOIN [histxyz] ON [xyz].[partnumber] = [xyzhist].[partnumber] WHERE [xyz].[cola] <> [histxyz].[cola] OR [xyz].[colb] <> [histxyz].[colb] OR etc...
through each of the fieleds that are hooked up to change tracking. Run that SP once, then use that temp table to generate customized reports based on parts per product which had a change.
3) Update weekly state snapshot of all parts remembering this week's state... transfer data from [xyz] to [xyzhist], so TRUNCATE then INSERT commands.
Seems slow and monotonous, the snapshotting "shell game" aspect... perhaps I may wrap that all into a transfer SP and allow the data to stay right on the server as it moves tables.
