Hello everyone.
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.
Any help is appreciated!
I created a Workgroup file (Project.mdw), assigned different Permissions to different Groups, and put different Users in appropriate Groups.
The above setup is working fine and just as required. But, if I remove or rename the Workgroup file, MS Access does not look for it, creates in its own Workgroup file and starts just as usual - without asking for the Password, or caring about the Permissions and/or restrictions set.
How can I make the database file bound to the MDW file, so that it does not open without it.
I created a Workgroup file (Project.mdw), assigned different Permissions to different Groups, and put different Users in appropriate Groups.
The above setup is working fine and just as required. But, if I remove or rename the Workgroup file, MS Access does not look for it, creates in its own Workgroup file and starts just as usual - without asking for the Password, or caring about the Permissions and/or restrictions set.
How can I make the database file bound to the MDW file, so that it does not open without it.
Ok.. I have done this before at another job, but this network (or stupid me) is giving me trouble. I'm trying to setup a database security (login/password) for a database on a network. I setup the security levels..setup a seperate workgroup... From my computer it logins fine with the correct workgroup.
I setup a link:
"G:Maximizer DatabaseMaximizer.mdb" /wrkgrp "G:Maximizer Databasemaxsecurity.mdw"
Under my network login it pops up with the correct login/password prompt.
On others, it goes into the database under "READ ONLY" but gives them access to the database in read only. It should using that workgroup.
Any suggestions?
Hi
I'm adding to a database that someone else set up. I went to the Design View page and clicked on one of the buttons at the bottom to add a text box etc etc. It all looks fine, but the field doesn't seem to be active - if I add some text into it for one page of the databse, the same text appears on every page of the databse. I notice that my "new field" is not listed in the fields list. How do I add it? I keep looking through "The Missing Manual" but without spending 3 days reading the whole thing (which I don't have time for) and learning much much more than I need to know just to get to the part that I need to know, it isn't helping me much.
Please can anyone enlighten me? My email is stu_paranormal@yahoo.co.uk
Thanks!
Stu
Hi,
I am fairly new to doing DBA, and I am having trouble adding a new column to a table that is existing. Is there any simple way to do this or does it have to be done throught code? And if so how.
Thanks
zorter8
I have a database with a backend on a network and the front end on each users PC.
When I add security in the form of a workgroup it only apllies to the front end and anyone can open up the tables on the backend.
How do I secure the whole database. Anyone have any advice on security.
Stephen
I have successfully used the recommended way to display images from a folder in a form as posted on the microsoft website.
http://support.microsoft.com/kb/210100/
These instructions were for Access 2000. I noticed that there are seperate instructions for doing this using Access 2003.:
http://support.microsoft.com/kb/285820/
My questions are:
1. If multiple users access this database using different versions of Access (2000 and 2003) will it not work for some?
2. do i have to modify code if i update to 2003?
Thanks for youir feedback!
~Bruce
Hi,
My database has 4 tables. Table 1 is assembly line 1 data. Table 2 is the sizes for assembly line 1. Table 3 is assembly line 3 data. Table 4 is the sizes for assembly line 2.
The table data comes from another program - they are reimported regularly and so I cannot change, add or delete fields from these 4 tables.
I have to change tables 2 and 4 to crosstab queries and then create 2 queries that join 1+2, 3+4. That's easy enough, no problem.
But then I have to UNION queries 1+2. While 95% of the fields are the same, the most crucial are not - the sizes. Assembly line 1 has 5 less sizes than assembly line 2. I need ALL of the sizes to show in the combined query.
I need to add these 5 fields without adding them to the tables. I did manage to create a crosstab query that included the missing sizes, but now I have a 1 in those fields where I need a NULL or Zero value.
Does that make sense? Can anybody help me?
Thanks in advance.
Rhet
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.
What can I do to fix this problem? Thnaks.
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.
Thank you.
Suzanne
Hi!
This is Kishore, working on VB Project which is using MS-Access95 as backend.
Now, i want to change the Database login Password.
Could anyone guide me in this context.
Regards,
Kishore
We are running two versions of Access (97 and 2003) on some of our machines. We recently set up a new workgroup file, but it seems that on the machines that have the two versions of Access the workgroup file reverts back to the old setting everytime the user logs in again.
What do we need to do to prevent the workgroup file from switching back?
Thanks
I run a school library database (Access 2003) and want to set up a password logon system so that different users can get at different parts of the program - e.g. Administrator (everything), Librarian (can add and delete records but not change the database design), Student (can only access certain areas, read only).
I've tried using the security wizard to set this up, which seems OK until you then open the database again. I would expect to then get some sort of log-on screen next time I open the database, but instead it opens normally, but then won't let me do anything because I "don't have permission". I had to restore a back-up copy.
I must be missing something obvious here. Is there a place to look for instructions? Couldn't find anything useful in the help screens.
Richard
Is it possible to have 2 or more users adding records into the same table at the same time? They would not be editing, only data entry.
I am wondering if this would cause a problem for the auto numbering for the ID field.
Hi everyone,
This is in regards to user security. I'm a relatively new user to Access (and this forum). My company uses Access 2000 and I'm taking over a database thats used by several departments at my company. This database contains sensitive information so I put user security on it using the wizard. Due to the nature of the database, a particular user group needs to have the ability to create new tables. The problem is this: No matter what I do with the user group security settings, I cannot prevent other user groups from creating new tables. Is there a way to prevent certain users from adding a table?
:confused:
Your help is appreciated
so i'm using MS Access security features, .mdw file and all that jazz. i'd like to market my program, but i don't want to have to add/delete users and change/add/delete permissions for every new/existing user. is there any way around this via an unbound form in vba, ie, something like "New User Name: _______" "New User Password: _______" "New User Permissions Group: (dropdown)"? is this possible, or MUST you go through the security page?
thanks
Hi,
I've been working hard at learning Access for past two months and spent a lot of time Googling and speeding through Alison Balter's books and at a slower pace the Paul Letwin’s Developers Handbook set (fantastic but I probably need a year to absorb the incredible detail).
I've built a prototype reconciliation tool using the recommended FE-BE model. I opted for a total ADO solution and have had great success in putting together a fast and useful tool for 10+ users.
I avoided using Workgroups in my design and developed my own basic sign-on authority model which allowed an Administrator (don't confuse with Admin user in Workgroups) to add new users who can use the Access app. The allowable users and which ones are signed on are stored in the BE. This all works reasonable well until network issues occur and the signed on user record on the BE is not reset as should be if the user signed-off genuinely.
This is where I realised I need to be able to monitor who is connected to the BE. There is a way of doing that using ADO which I can get to work. I then noticed because all users are signed on with Workgroup Admin as default I could not differentiate between users. I then decided to implement Workgroup authority retrospectively.
I decided to place the .mdw on the LAN with the BE (this seems to go against conventional wisdom but could not workout how else I could achieve what I wanted to). This enables the two Administrators in different places to maintain users via the FE. I use the /wrkgrp command line flag to point to the correct .mdw.
I then started getting all sort of problems . . .I'm still in testing . . . not so bad but deadlines are looming and I'm worried.
Sorry, I digress. . .the problem I seem to be getting is when I open the FE :
Run-time error -2147217843 (80040e4d)
Cannot start your application. The workgroup information file is missing or opened exclusively by another user
I also have problems developing the FE with the workgroup file in place. It seems to complain about another user is locking the FE.
The problem is a little verbose but just trying to paint a picture . . .now, this is what I'm after. . .I need the following ability:
1. Two Administrators who can maintain users. When a new user is added the Administrator chooses a password.
2. When the new user signs on the user is prompted to enter new password.
3. The administrators can view who is genuinely signed on and reset accounts appropriately.
I am currently studying the Access Security sections in the Paul Letwin book to better understand what is going on. It does seem retro-fitting an app to a workgroup model is not straightforward. Admittedly, I should have considered Workgroups in my design before starting (I will know).
Thanks for staying with me if you're still reading . . .any suggestion/pointers would be great.
Lastly, using Access 2000 : O/S W2000
The purpose of this project is to aim the security mechanism an allow and restrict of individuals or group of individuals of the database. Define the security accounts and groups of users allowed to access.
Users: Can view / add / edit of data into the database.
Superintendent: Has view access to database but is limited only to their section.
Manager: Has full access to database but is limited to their section.
Administrator: Acts as the overall administrator for the database. Has full control over all data and objects contained in the database.
Most likely the closest example of this database is annual leave application. If individuals is/are adding data and only his immediate Superintendent can view with limited to his group and the same with the Manager as we have four (4) sections (Finance; Procurement; Services; & Management) in one unified department.
I have created a database for 2/3 users (will progress to more once the system has been smoothed over) who will have the db.file open from 9-5 and will be consistently adding and changing data within 2/3 forms. Most of the time but not always a message comes up saying,
"You do not have exclusive access to this database at this time. Any changes you make may not be allowed to be saved later"
I can understand that it can create data corruption if multiple users are allowed to edit and modify the same data at the same time but surely a database can't be that limited. I thought that splitting the database into a front end on a local server and then a back end on my computer would solve the problem but everyone who is using the front-end still experiences the same problem.
How to be able to overcome issues with multiple users access the same forms and tables? Even when another user is editing one form and another is editing a different form the message will still appear.
Hello,
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard.
But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007.
I can't use the Package Wizard.
How can I do to solve this?
Thanks.
I have two database applications and they are:
- the (A) application is for administration use.
- the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables
Dim db As DAO.Database
Dim qdf As DAO.QueryDef
Dim varItem As Variant
Dim strCriteria As String
Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM
qryContractListSummarybyDateContract3TYPEBREAK WHERE
qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri
Masonry NSW');'
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks.
Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset
Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset
Dim ObjXLApp As New Excel.Application
Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String
Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer
Dim TotalBlank As Integer, R As Integer, C As Integer
Dim BadSheet As Boolean, ImpFail As Boolean
Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then
MsgBox ("You must select a Program to load.")
ObjXLApp.Quit 'Exit from MS Excel
Exit Function
End If