I searched and doesn't seem to find anything about that question.
I am aware that there are forms that help with building dynamic queries for end users who need to juggle their data, but wondered if allowing them to access QBE would make everything easier (why reinvent the wheel?), and whether it is possible to restrict QBE from doing action queries or using dynaset to restrict end users from updating via queries which may circumvent the rules written in forms for the given data.
Have anyone had designed database with users having access to QBE? If not, how do you provide as much functionality without practically having to re-invent the wheel?
Has anyone got any ideas of programs that are avaliable to kick users of a database in Access remotely?
Our Programmes team have a program which will do this and it doesn't involve any tables, etc within the database but they won't tell me whats it called or provide me with a copy of it!!
Is there a way in Access 2000 that I can set up a users table? Basic info:
Name Phone Number Fax Number
Then every time the database is opened they are prompted for their name?
I have a database that has a Fax Cover Sheet within the DB, when they click the Fax Cover Sheet Form I want their information to automatically be generated into the form based on the information from the original table.
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'm having some issues with a database that I have created. All this time only one user would be in the database. But now I have 2 to 3 people at a time in the database. I get an error and its not letting the users put any information in.
I have it split into a FE and BE. I have it set to share. Any thoughts or suggestions?
I'm responsible for an Access 2000 database which three people have open more or less constantly and another four open from time to time.
The database is on a P2P network and is split, with the back end in a single location. The network is wireless.
At the moment there are no problems with this setup but changes are being contemplated which will mean that eight people will have the database open constantly with another four using it occasionally.
For other reasons ( There were only three other wireless networks within range when we started, now there are eight), we are switching the network from wireless to cable. The back end will be transferred to a new PC with a powerful processor and loads of memory.
Does anyone have experience of allowing that many users to log on at the same time in a P2P network? And was the experience good or bad?
Im totally new at all this stuff, so any help is appreciated.
i have a database with one table that has many different attributes and almost 3000 records. this is all i have done, i have simply been loading in all of the data to the table, now that that is done i need to allow users to extract the data.
so, what is the best way to build a front end that allows the user to easily extract data from the database? ideally, i would like to have some sort of front end that would have a text input window where they could search for records matching attributes in the table that match or are close to the text they type in, with some additional options for honing down the search terms with dropdown menus, radio buttons, etc.
the problem is i really havent a clue on how to do that stuff. can anyone just give some general, beginner type steps for things i should be doing to create that "front end" i am visualizing. THANKS!
I have a database that i created for our tech support team. I have split the database and have given the 3 users each a shortcut. I als e only installed Access Runtime on their machines.
The first user in pilot testing had no issues and we have just added the other 2 users. At first all was well. However, the 2 new users are now having periodic lock ups where they go to enter a new record and the dbase freezes on them. It seems to release itself in a few minutes, but this does not help my productivity.
My original user is still not having any trouble. Does anyone have any ideas of something that perhaps I missed? Everything I have read, suggests that 3 users should not have any trouble using a split dbase.
Is it runtime that may be causing this? I have considered going to full versions if need be, but then I would need to figure out how to lock it down better.
I have developed an application for a friend. We live about 100 miles apart in the UK. The database (Access 2007) works perfectly for us, I input data from various sources and he views the reports I've designed that show him exactly what he wants to see.
Now I want to move to the next phase which is I enter data from my PC at home and he then views the reports on his PC at his home.
I am trying to get a feel for how Access 2007 performs regarding the ammount of concurrent users using a database.
I know there has been a lot of differing opinions about previous version and was wonder is the new version of Access (& I would guess Jet as well) is more stable with multiple users?
I maintain the Access databases at the hospital that I work at. Last weekend, our server went down. Computer Services got a new server and reworked the networking permissions. However, Access will no longer allow more than one user to open the database at a time. This is a problem because we always have multiple users that need simultaneous access. The default is still "Open Shared" and I checked to ensure that the databases are not being opened exclusively. However, the message that I do get when a second user tries to open the database is:
The table 'MSysAccessObjects' is already opened exclusively by another user, or it is already open through the user interface and cannot be manipulated programmatically. (Error 3008) -
I understand that this message usually comes up when I try to open a table that is already being edited elsewhere. I have the record locks set to "edited record". However, this is a system file, so I am hesitant to make changes in it unless I know exactly what I am doing. This is a problem that we have never had before but for some reason was created after our server went down. I don't know why something changed or if this table is absolutely necessary. I am unsure where to start to solve the problem.
I know that Access probably permits around 20 or so users to simultaneously access the database before it start to become unfriendly. However, I have a database that would require 200 or so users grabbing around 1,000 rows of data via an Excel ADO connection to the backend tables.
So they would never need to physically go inside the Access database its self, but instead it would garb data by opening an ADO connection to the database > Grabbing the data > Closing the database connection.
Is this okay to do with around 200 users simultaneously querying the database tables via an Excel ADO connection?
I am about to allow users to access a database I redesigned for others to use.I am trying to save it as an ACCDE so they can't mess it up. The database is very very simple.6 tables each with only 4 fields or less... and none are related to one another
7 forms. 1 report. 0 queries... it's just a SKU generator.
When I attempt to save as ACCDE I get an error that reads."Microsoft Access was unable to create the .accde, .mde, or .ade file.This error is usually associated with compiling a large database into an MDE file.* Because of the method used to compile the database, a considerable number of TableID references are created for each table.* The Access database engine can only create a maximum of 2048 open TableIDs at one time.* Exporting a database as an MDE potentially can exceed this limit if the database has a large number of objects (table, macro, form, report, etc).
There is no accurate method to estimate the number of TableIDs the Access database engine uses during the process of compiling a database as an MDE.* However, each VBA module and each form uses one TableID, as a result, if the database has 500 forms, and each form's HasModule property is set to Yes, as many as 1,000 TableIDs are used."
This morning I accidently ran the "User-Level security wizard" on a secure database that we use. I meant to add a member but clicked the wrong thing and followed suite by hitting "Finish" instead of cancel because I wasn't paying attention. Aside from creating a "Security.mdw" file which isn't being used at all, it also somehow managed to lock everyone but the administrator out.
I checked the Users/Groups and Permissions, they are all there and correct, nothing seems to have been changed at all but when anyone tries to log in now they get the following error:"You do not have the necessary permissions to use the '...mdb' object. Have your system administrator or the person who created this object establish the appropriate permissions for you."
I've read some posts with similarish issues that recommended recreating the .mdw file and importing the data over. The file is encrypted so I wasn't able to do that but I did try making a copy and renaming it then changing the path in the Access shortcut to the copy instead. What all files/settings handle this and if the Users/Groups show up correctly in the database, what could be preventing the users from getting in?
I have an MS Access application for about 40 users. The problem is that the company does not want to have to buy all these licenses and put it on each machine. Also because each person had to bring in their own set of data multiple people cannot be hitting this at once. So they want to know if there is a way to allow the people to use it without having the application on their machine; and thereby saving the money of buying 40 licenses.
I have an access database that is used as a front-end application to a sql server 2000 database. Users have adequate permissions to access database and functionalities but a few are receiving the following error message:
I would like to use an Access database over an Intranet. What are the limitations of doing this? I want multiple individuals to be able to open forms and enter data. I would also want others to be able to run queries and reports on the database. Would I need to upsize to an Oracle database to run with multiple users? Any words of wisdom would be appreciated.
I have a fairly complex database with a lot of charts, reports, forms etc.
My problem is that whenever someone chooses to maximize a Pivotchart, a report preview or other things, they usually click the big X button in the top right hand corner and close Access entirely. They don't think to click the smaller x button right below it.
This is frustrating when they just want to go back to the switchboard to performs some other task. They have to restart the database, log in...etc.
I know you can prevent forms and whatnot from being maximized, but I do want them to have that feature for a number of reasons... especially with my Pivotcharts. They are much clearer when expanded to full-size.
Is there a solution to this problem, or do my users just have to be more careful?
I've a BE/FE database where the BE is on the server and the FE on different PCs. I have got linked tables in my FE and the connection between them and the BE is correct; however, users cannot view data entered by others. They can only view data entered by themselves!!
I'm not sure if the records are getting locked that's why they can't see others inputs.
Hi, I created a database where everybody should insert his holiday plans and absence of business. the Database is linked and opens automatically the form when you click on the link on the pdf. But know it is not possible anymore that more than one person opens the file to insert the data. The mistake is: Could not lock file! What do I have to do that more people can use the database at the same time (not only read-only) Thank you for the help
At work we have a terminal services setup for most of the staff which is being configured now. We have hit a snag with access security settings basically we need macros to run for relinking odbc databases and various vba functions (some run overnight so we don't want to deal with the security dialogs). We though the best way to do this would be setup trusted locations. We did this logged in to terminal server as admin hoping this would be a machine level setting but it seems to be on a per user basis.
Is there a way to set a trusted location for all users of a machine I have google and come up with nothing. The other option is enable all macros which I don't want to do.
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.
