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 would like to limit the number of users connected to a shared database. Each user opens a database as the default 'Admin' user. Does anyone know how to do that without user authentication? What event occurs when a user opens the database? How to supervise the ldb file that manages shared usage? I suppose it should be something with the Workspace object.
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've been using Access 2007 to run queries on a database where we eventually export results as separate Excel spreadsheets for individual clients. The process is quite involved, using queries to change fields from code letters to words and splitting the database up into different client tables, saving the tables under date order and with different client codes.
I now need to pass this role on to colleagues, so need to make everything as straightforward as possible.
I had thought to use a Form as the user interface, with a minimum number of buttons, however I need either the system or the user to amend the date for the initial table, then to use this new table and run a series of standard queries on it, then produce the separate tables.
I don't think I can just use macros behind the buttons, because the database name is changing each time.
I assume some parts will be too tricky to automate - it will be necessary for colleagues to follow instructions instead.....
I have designed a database which I intend to split for multi-users to access from one front end icon on a shared folder at work. I have designed a form bound to cmr record table and on it a subform to another table where cmrs activities will be saved. The form has buttons to and blank controls.
User can create a new activity entry by typing into the blank controls and pressing the save button which saves to the activity table. the edit button extracts a selected records details (selected on the subform) from the activity table and populates the blank field for a user to edit and then hit save to save changes. The delete button deletes a selected record from the activity table. I intend to have multi-users either accessing, viewing and a possibly editing the same customer at the same time. The simultaneous viewing is essential but the simultaneous editing, though not desired is inevitably going to occur.
What I would like to know is:
1. Can you lock an individual record in a table or does the whole table have to be locked. E.g If Colleague 1 is editing Cmr A's record in Table1 can he lock it so Colleague 2 can view and edit Cmr B's record in Table1
2.Can Colleague 1 access/read Cmr A's record in Table1 to retrieve details toe the form controls if Colleague 2 is viewing or editing Cmr A's record in Table1
3. If record lock is possible, how can I initiate it in my example code below.Edit activity record Code
Code: Private Sub Edit_A_Click() 'Get Data to text box control With Me.R_P_Data_P_Subfrm.Form Me.txtrID = !rID Me.txtrID.Tag = !rID Me.txtrefNo = !refNo Me.cmbrpc = !rPC
I need to develop a database for HR department for hiring. There are about 30 departments in the office and these departments are distributed among 12 HR officers. Each HR Officer works on 2 or 3 of these departments at a time throughout the day. Currently the HR department is using Excel Workbook to keep record of each department (hence 34 Workbooks in use). I want to convert this system in Access.
Now the problem is that I am confused how to handle these department. To keep record, every department has exactly same type of data. I was planning to make one table for each department and make one form to enter data into each table (hence total 30 tables for departments). This sounds weird approach. I have done this to avoid concurrent access problem.
If I make one table to keep data of 30 departments and one Form for entry, will it be possible for 12 users to open the same DB, open the same Form and Insert/Update the same table at the same time? What approach should I follow?
On trying to import an Excel 2007 file into Access 2007 I get the following:
1) Choose "External Data," Import, Exce 2) Select small file in MS Excel 2007 format. 3) Click on Import the source data into a new table ... 4) Choose OK
Immediately get "Microsoft Office Access has stopped working. Windows is checking for a solution to the problem..." This message never resolves, so I have to click 'Cancel'.
Then I get "Microsoft Office Access is trying to recover your information..." I have to click "Cancel" here as well and then kill MS Access in Task Manager.
Event Viewer gives following message, which is of no help: "ID: 2, Application Name: Microsoft Office Access, Application Version: 12.0.6211.1000, Microsoft Office Version: 12.0.6215.1000. This session lasted 710 seconds with 120 seconds of active time. This session ended with a crash."
Trying to import a small Excel 2003 file leads the same result. The same happens with a CSV file.
I have uninstalled and reinstalled Office 2007 as well. I am using Vista Ultimate.
I installed Office Enterprise 2007. Then I installed DEveloper Exrtensions, then Access Runtime 2007. All appear to have installed OK - they appear in Program and Features. Instructions on runtime packaging tell me that a Developer option should appear in the resulting drop-down when I click the Office button (top-left round thing) when I have a d/b open in Access. It's not there! I have un-installed and re-installed the extensions and the runtime - still nothing! Help! I do have Runtime 2002 (XP) on the same PC, is that relevant?
I'm trying to create a database that is going to be used to deliver some work to several of our users. Each time they open a specific form they'll be delivered a job.
Now it works like this, the user gets an ID_JOB from queue
In the form they get all the all the work orders with that ID_JOB, the thing is i'm getting users with same duplicate orders cause i can't update the locked efficiently.
Regarding the users, the database is split, multi-user, with >30 simultaneously
I'm been trying to use dao.recordset, with transactions to try and reduce the duplicate orders.
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.
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.
Background Info: I developed our main department's Access 2003 split database which is on a server for 15+ Users. I've now been given Access 2007 for development -- Users still have 2003. There are also 2 other smaller databases that are not split (.mdb).
Problem: In the split database, I've saved the Application .mdb as 2003, relinked and made a new .mde. But the Users still cannot open the database. (I did this in a copy until I figure out the nuances with 2007.) The 2 other unsplit databases can be saved as 2003 version and Users can open OK.
I'm grateful for any suggestions on working with Access 2007. I've been trying to tackle the ribbon which is a whole other question.
Having a problem here after installing 2007. All my previously created databases work fine in 2007 (after clicking the enable, which is a pain,but don't know any other way) When I return to 2002 and try to open the databases I get different errors all something like this on....... "The expression On Open you entered as the event property setting produced the following error: Object or class does not support the set of events. Whats up here?????I have found a site here...http://allenbrowne.com/bug-17.htmlMentions this problem,but refers to Vista..... Does the same apply to XP? And which is the best fix?
I have an Access 2000/2003 database which opens up and displays correctly in Access 2007, but when I go to use the File>Print command, or for that matter any of the other pull down menu's nothing happens?
Has anyone else experienced thisproblem, or does anyone know what I am doing wrong?
I have created a database in Access 2007 that now works well, and one that I'm quite proud off. However, I can easily convert it to an Access 2000 format as can anyone else here, but when I load it up there is a major problem.
I have used the tab control in my main form and that has three tabs on it. However, it's positioned correctly in Access 2007 it's not positioned correctly in Access 2000 as I have to move the tab control down a bit, but that would seem fine. So I lowered the tab control form and changed my form layout slightly, but even then the tab control over all over the Access 2000 form whenever I interact with the tabs - most bizzare.
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?
I recently heard that Access 2007 ( part of MS Office 2007) can be purchased as a stand alone program. This sort of confirms that : look at pricing breakdown on : http://techrepublic.com.com/5254-6257-0.html?forumID=99&threadID=174062&messageID=1961442&id=3053951
I have downloaded Access 2007 trial, but I don't know how to use some of its features. When I try to open any of my databases saved as A2000, it displays a security message. "Security Warning: Certain content in the database has been disabled"
Hi, I have downloaded the access 2007 trial. Installed and registered it with the trial code. However when I try to install any of the free sample dbs from MS including the northwind db, Access crashes!! I was going to purchase the full version of office, but wanted to test access first. If anyone knows a solution, or can email the northwind 2007 db it would be appreciated.Many ThanksP.S. Screen dump of error is included.
I read this article from Allen Browne http://allenbrowne.com/Access2007.html#Bugs Has anyone had any problems with 2007, data, tables, etc. Our company would like to install, but after reading this, just second guessing myself. We have not yet installed the SP1. The company is gang ho about running with 2007.