I have a split MS Access database that 3 different users are utilizing, each with their own copy of the front end in different locations from the backend. There is also a copy of the front end in the same drive/folder as the backend. When I run reports from the front end located in the same back end folder, they are fine. When run from another drive/folder location, the reports run, but don't have a complete set of data. Any advice on what might be causing this? Thanks!
You can get access errors by having multiple users trying to change the same recordset.
Could you implement a SQL backend, and link all the individual ACCESS DBs to the SQL server? This would limit the possibility of multiple versions of the same data.
Related
I'm in a situation where I need to use a SQL server as a back end to Access 2010 database. The problem is that the server is only accessible with a SQL login. This isn't a big problem for the table part of the database - one login to the server connects all of the tables. The problem is with stored procedures that must be called. Since these are not under the ODBC umbrella, each query requires a login. I can't seem to find a way around that. Currently, I'm trying setting up pass through queries in Access, but once again - each query has to be logged in to individually. Is there a way to set up something (query setting, ODBC setting, VB structure or anything!) that will get around this problem of having to log in every time an SP is called?
I'm trying to avoid writing a whole big wrapper that handles the login and holds the password for later connections...
I have an MS Access 2007 split database. The Back End database contains 1 table. It is on a shared drive and front end has a data entry form with Macros, also a linked table from back end. Everyone in the organization has same version of Access (2007), same operating system etc.
Problem is I am able to open and add records to the front end but when anyone else try to open the front end it comes up with "Unrecognized database format" and they couldn't open it.
So far tried changing New database sort order to general - Legacy/ Compact and repair database from database tools but still not working for other users. Almost spent half a day searching and trying various solutions without success. Any help into right direction will be highly appreciated.
The lock file got corrupted. Delete it and re-open the application.
The Problem
I have been encountering a problem with MSAccess 2007, with a 2003 format database.
When I try to run the query (for example a select query), I get the message "The Microsoft Office Access database engine cannot open or write to the file "query name". It is already opened exclusively by another user or you need permission to view and write its data".
In addition, I cannot view the query in design view, only in SQL view. This only happens for certain queries, which I was previously able to design and change with no issues.
What I have tried
I have tried Repairing and Compacting, and that does not fix the problem. The only way I have been able to fix so far is by importing all the objects into a new database, which has resolved the problem for a while, then a few days later the same issue happens again.
If you are in a multi-user environment, and the back end database is on a share drive, this will happen when someone else opens the back end database directly from the shared drive instead of using the local front end database. If the back end database is opened directly from the shared drive, other users will be unable to use the front end database due to locking issues.
I have an MS Access database on a network drive with a userform which has multiple users (All using at the same time)
The form runs an update-query which will add data into a raw data table.
Does anybody know how I can make this work if two(or more) users run the update query at the same time? I assume this has to be done using temporary tables...
Thanks,
James
Just to add some pages from my website to this discussion.
You want to split the MDB into a Front End MDB containing the queries, forms, reports, macros and modules with just the tables and relationships in the Back End MDB. The FE is copied to each network users computer. The FE MDB is linked to the tables in the back end MDB which resides on a server. You make updates to the FE MDB and distribute them to the users, likely as an MDE.
See the "Splitting your app into a front end and back end Tips" page for more info. See the free Auto FE Updater utility to make the distribution of new FEs relatively painless.. The utility also supports Terminal Server/Citrix quite nicely. Also visit my Access Performance FAQ page.
Access does not behave well if the entire database (front end forms plus backend database) is accessed by several users from a network share.
Try splitting into a front end (one on each client machine) and a single backend (tables) on the network share, and use linked tables in the front-end.
How to manually split a Access database in Microsoft Access
Information about query performance in an Access database
Microsoft Access Performance Tips to Speed up Your Access Databases
Tony Toews' Microsoft Access Performance FAQ is well worth reading.
I would like to be able to programatically add a user to the report server by creating some stored procedure that accepts user_id and does inserts into ReportServer..Users and other associated tables. I am having trouble doing this (especially the column ReportServer..Users.Sid).
Has anyone been able to accomplish this in the past?
The end goal would be to have a script on my local PC that connects via osql to add users to the database so they can ad-hoc query and also add them to the report server so they can have access to the reports website. I have gotten the database access working...that was fairly easy. Having problems with report server.
Thanks!
You don't add users to RS this way. It's a seriously bad idea.
Why not just add "Everyone" into the "Browser" role? This is effectively what you are doing...