General :: User Updates On Front End Database Not Updating Back End
Nov 12, 2012
I have a Database that has been split into two.
Back-end for all the data.
Front end for all the forms and queries.
The front end has been saved in a accde format and distributed to 20+ users. They have all saved this onto there computers and this is used as an application.The users complete a form on a weekly basis on the application and then save. This then saves into the back end.For some reason I have noticed that a few users submission randomly do not save. For the life of me I cannot understand why.All users have saved them into the back end in the past but every now and then submission for users do not save.
Using Dropbox to host a split database. Ulimately I would like to create a run version for users with the back end held in a drop box directory.
As an unsplit database everything is working fine on dropbox records are saved in a timely manner and great.
Once I split to FE /BE only some records are saved on the BE and some are dropped. Was getting conflicted copies of Back end but manged to stop this happening but the records were noit on either copy.
Gave each user their own FE (on a drop box directory) linking to a BE in a sub directory on the same dropbox.
The key issue is that not all users have access and I don't want them to get into code so want to aim towards a run version.
I have designed a split database( with back end and front end), I am just wondering what would be the best way to put a password for both of the back and front end.
I have split my database in Front End och Back End, and both are password protected. The Front End has been converted to ACCDE.
When I try to import to Excel from Front End and/or Back End using database connections I receive a message telling me that I am using an invalid password (even though I use the same password when I encrypt/decrypt FE and BE). I've tried using Access import, ODBC and Microsoft Query. (In some cases I 'm also prompted to set a username, which I do not know which it should be since I haven't set one in my database (except the automatic "admin"))
I have a split database. My backend Relationships aren't updating to my front end. How do I get my front end relationships to update to what my back end looks like? All tables are LINKED not imported.
I have a Access data base (2007) which i splitted and store the back end database in a file server where all users have full control and the individual copies of front end put in the users computers. Unfortunately when one user is using the programme, others can not use. Following error msg appears. Both back end and front end are running under shared mode ( not exclusive ).
"Could not use xxxxxx_Be.accdb; file already in use."
I need help making a front and back end to my database. How should I do it!?!? All I know is what I should put in the front end and what goes in the back end. The rest needs to be explained to me somehow...
I did a search in here as well as Google to figure out why when I relinked the front end to the back end after adding 2 tables to the back end that the tables did NOT show up on the front end. Only the original tables that I began with.From what I have read there are different ways to do it. One suggestion on here was to create the table on the front end and export it to the back end. I guess I will have to do this going forward.
But my question is, after searching pages upon pages with no luck, since I already have the tables in the back end how do I tell the front end to find them and link them?
Objective?: I'm attempting to change the file location of the back end portion of my split database.
What I've done so far: I've used the linked table manager to update the back end location of all tables in the front end portion of the database.
Symptoms: When making a change to the OLD back end: If I change the name or move the old back end and then try to re-open the front end, Access opens as if I'm opening the application itself without any database associated with it until I restore the OLD back end to its appropriate state.
When making a change to the NEW back end: If I change the name or move the new Back end and then try to re-open the front end, I get a: "Could not find file" error message until I restore the new back end to it's appropriate state.
I've just discovered a query that I think put me one step closer to resolving this issue. [URL] .....
When I run this query:
Code: SELECT MSysObjects.Database FROM MSysObjects GROUP BY MSysObjects.Database, MSysObjects.Type HAVING (((MSysObjects.Type) In (4,6)));
It returns 2 results: 1. The path of my old back end 2. The path of my new back end.
Unfortunately I'm not able to update the values from the Datasheet, but this does confirm to me that the old back end is still some how being used by the front end even after my tables have all been updated.
My question encompasses a front end connected to multiple back ends. It is probably a mundane point, but reading a few articles didn't seem to touch on it.
By this, let me toss out that I am thinking of the personnel where I work when I say 95% have a hard time using email and MS Word, let alone mundane functions like find a file, etc. As such, I have to make my front-ends extremely user friendly.
With that in mind, when developers have multiple back ends, what are thoughts about the best way to relink when required? Even when there are 'more sophisticated' users? Security not an issue or is an issue (inasmuch as can be handled in access)?
Ex: Large corporation with a multitude of user ability. Large database with say 3 different back ends.
I was thinking about keeping a front-end table with each table name and UNC path, hard coding paths to corresponding table names, etc.
Personally I don't have a need for multiple back-ends, but the question came up while reading.
I am trying to create a navigation form on a split database with front end and back end.But Access is not letting me drag forms or reports into the navigation form. Why?
I have a 2007 back-end db on a network share and around 15 regular users who access it through their own front-end db/interface. One user on Windows 7 is able to launch and use his front-end copy fine except when he goes to launch one form for data entry.
This form clocks and freezes the entire application. I sat with him and was able to determine that the issue is that the form_load code is never running. He clicks on the button to launch the form (done in vba) and the code never runs. If he opens the form in design view first then changes to form view, the code runs fine and there are no issues. This is his present work-around, but I had to give him an unlocked FE copy to pull it off (not ideal!).
I tried this with him on different PCs, with different front-end copies, and even in the back-end copy. Same result each time. None of the other users have this issue, and he can replicate this issue on different PCs. I'm at a loss for what might be causing this since it really seems so user-specific.
I am splitting a database and have created the Back end already. When I create the front end and link to the tables on the back end... The front end does not link to all the tables in the back end. The list that comes up when creating the linkings does not show all the tables in the back end. What would cause this?
I split my db last week and put both front end and back end files in a shared network folder. I backup the db every day to a different folder on the network server and also to my laptop. I usually backup right after a form update so that the latest version of the form is available to users who want to update their local copy of the front end. I've been sending email alerts to the users.
My question is this: What is the best way to (1) make sure my backup updates the front end on the network server and (2) how can I automatically alert users to update to the latest version of the front end?
I want to create a database that keeps track of contributions of members of an association. Every member can voluntarily give a standing order to contribute a fixed amount every month. A member can as well decide to review his/her contribute.
how I can come up with a database that can automatically add the contribution of a member monthly without manual input since the stated contribution is known. So that I can run a report for individual member and the report can capture the every monthly contribution that has been added automatically and shows when ever a member changes his/her contribution amount.
I have built a database and within it my queries I use for reporting make tables in a separate database. This allows me to work in my data base and update info as needed. My problem is that my make table queries wont run if anyone has one of the report pivot tables open. I have added macros to all the Excel files that pull from the reporting DB but I still have several times when I cannot update because someone is using the pivot table, Is there a way to allow me to update the report DB's while the pivot tables are open? I have tried using manual refresh methods and disabling auto update on open but the result is the same.
What is the best solution for sharing a front end DB as me having the BE installed at my pc, giving all user the FE and then refreshing table link with BE installed at pc but the problem is that the shared FE becoming slow any option ? as only 5 users using this at a time.
I have a database system into the back end and front end and then created the accde file with the front end file to give this to users on their computer. The back end being placed on a server with a path of type servernamefolder..I have used the Linked Table Manager to point to the tables server name folderfilename.accdb
but in doing this I get a message Windows cannot access servernamefolder..is this to do Network Rights on the server that I don't have permission to access the server and folder.
I've prepared a front end database with forms that allow data to be keyed into linked tables to my main databse.
However, currently the front end database only allows 1 user to do it at 1 time and when another user tries to open the file, an error "The Database Has Been Placed in a State by User on Machine That Prevents It From Being Opened or Locked'
Is there anyway to allow multiple users to use the front end database at the same time?
I have a database application that i intend to split with the table part on a server and the forms part on each users desktop. It will be used by approx 10 users. While the probability of different users accessing and updating the same form is small, the possibility exists.
Is there a way i can prevent any weird multiple update stuff happening? I'm using Access 2003
I was looking to see if there was an easy way to create a user front end desktop application for a small access database.I have three users on different computers i would like them to input or amend data within one table of the access database.
I have a split db that has been in use for a few years by about 12 people. The front end is compiled into an accde file.
Ocasionally a user (randomly) might get an error message "Microsoft has detected that this database is in an inconsistent state...." when closing the db and when that happens, a copy of the front end is automatically placed on their desktop.
This front end is always deleted and the original front end continues to work just fine afterwards.
Why are my users getting this error message? Why is the front end automatically copied onto their desktops?
