I have a database that I've created for someone else to use. It's split into a front and back end. The user will be placing the front end on her desktop PC and the back end on a network server.
She also will be taking the database home to use from time to time. My problem is that when the database is split, upon opening, it looks for the back end on the network drive, which is unavailable when she's away from the office.
Is there a way to tell the Access to look in a directory relative to the one it's in?
So the database I have right now is split, with the back end on our server. Everything has been going great, however there are several second time delays when loading large forms, queries, etc. I've heard that moving the back end to an sql server is the way to go for speed.All forms and queries are on front end of database. Tables are located on the back end which is sitting on the server.
I have a client that is using a split database. I am working on an update to the program and need to transfer a table to the backend that has the correct structure and information included in it. My thoughts are to make a one time use program that transfers the table to the backend. I have seen DoCmd.TransferDatabase and DoCmd.CopyObject as possible ways to go.
I have created a few split multiuser databases in Access 97 that my company has used over the past few years. Currently, we are trying to move everything to a new network server. When I did a simple copy and paste on Friday moving everything to the other server it seemed to work fine. Until I tried to open any of the databases. I kept getting the message that they all were read only.
Do I need to bring the database back together before transferring it? I also plan on converting the databases to Access 2003. What precautions should I take in doing this?
Thanks for any and all information you can pass along.
I am working in Microsoft Access 2010 and wanted to move tables from a number of databases to a "Master List of Tables" without having to manually recreate them. The purpose is to have this "Master List" available when we are creating new databases covering similar topics.
I was hoping to use the import tool but it appears to address only data not tables.
Hi Everyone, I am attempting to move a password protected database to a different folder on our shared drive but I am not sure the steps that are needed to do so. The database is already split. Can someone please assist???
I am attempting to move a secure database location. How do you change the location of the security since it is still trying to read off the old location. The database opens up fine with the passwords. Then I deleted the old folder it was in and try to log back in and give me the security upon startup error. So my problem is how to I change the security upon startup. I see you can change the location of the unsecure through a wizard but how about the other way??? I think I am trying to change the Workgroup information file but how do i do that??
I am new to Microsoft access. I have a database moved from another computer. it is split into the backend and the front end..
However, when i click on the forms in the front end, I get an error message. It is trying to use a path from the old computer, to the database, but its on a different computer.
So, this brings me to my question, how do i change the path, to the new location
I'm using Access 2007 which I built a database that runs queries off of tables using ODBC. The database is all done in ms access, I've used no visual basic programing on it. I'm now trying to move a copy of the database to another computer's local drive in the office. When we try to open it on the other computer it gives me an error that says "There was a problem sending the command to the program" and Access hangs, which I then have to run task manager to end the program.
Specs Are: Windows 7 64bit (the db was created on Windows 7 32bit)
Currently I have an Access dB that was developed in A2003 but we are currently using A2010, it is accessed by multiple users that all have a frontend locally on there own networked PC's, with the backends etc on an old NT server, we are having problems with new technology accessing the NT server so it's well past time we got shut of it
We have a share on our network that has been made available to us to migrate all our NT server files to, Here's my problem, on testing the procedure I copied the database backend and .mdw file over to the share then tried to open the dB where upon i got the following error message
Cannot open microsoft Access database information file
On further investigation it seems that both the back end and the .mdw file have copied over with no content i.e filesize is 0kB, not only that the originals also seem to have had there content "deleted" a simple copy shouldn't have done this (I did have a backup btw)
Hi, My access database's tables are currently linked to an excel document. My question is, how do I move my database to the network? Currently when I move the the database to the network no one can open my tables because the link goes to my documents on my computer which they can't access on the network. So how do I move the database and maintain the link between the database and my tables?
Moving to new computer, both under Win XP pro, Access 2003. New computer is MacBook Air running Parallels. Transferred Access database via an external hard drive. Now the data shows up as Read Only. Is there a procedure to run down the cause and make the data accessible?
:confused: I have read a quite a few threads on spiting the database. My database is 50 Meg and running very slow. I have compacted and repair, still the same. This just happen all of sudden. Could that be possible?. What should I look out before I try to spit it?. It’s given that I will make a backup. I am running Access 2003. I have over 150 users.
I am almost at the finishing line with a great deal of help from here. I have now normalised the tables, built complicated queries, forms, reports, all from scratch as I knew absolutely nothing before I started with Access three months ago. I have compacted and repaired the database using the wizard, and also complied the code and analyzed all tables, forms, queries, and reports and relationships. The final step is to make it an MDE file so that it can go on the local network at work (not on the internet). My questions are these;
Do I need to split the database into front and back ends?
If I save a copy of the original MDB file and then make it a MDE file would that not suffice in making it run more efficiently?
Can a split MDB database be made into an MDE database?
I have a database that resides on a file server share. I have split the database to create a backend. I then posted a shortcut of the front end to the desktops of two users who have access to the share. I then tried to access the front end from the two machines simultaneously. It opened on the first PC but not the second? When I viewed the server share it had a 'padlock' icon?
Where am I going wrong? This is the first time I have attempted this scenario!! Thanks in advance, Phil
Should splitting only be done when all tables,queries,forms,reports, etc. are done. Or can it be done anytime. I am almost to that stage but didnt want to jump the gun and run into problems later on.
I was having a discussion with Rickster57 concerning my newly developed database, and he recommended that I split it so that it has a front end and a back end. Rick listed a number of very good reasons for doing this (so I will definitely do it). But I wanted to pose the question so I could get some of the reasons the more seasoned Access programmers have for creating a front and back end to their programs.
I recently split my database and also used Bob Larson's Autoupdating tool. Everything appeared to be working fine until a few users were unable to access the db. I later found out that because they are at a different site, they don't map to the server that houses the database BE. However, even if they manually map to the correct server, they are unable to bring up the db Form. They get an error stating the BE "...is not a valid path". My questions are:
1) If I were to copy all the files (the Master FE, BE, and MDE) to a public folder that ALL users have access to, will everyone be able to bring up the database Form?
2) How would this affect what was already set up when I ran Bob Larson's utility (or even the splitting and MDE creation)?
3) Is there a way to "Undo" what was previously "Done" to this database (ie: Splitting, Larson Utility, MDE creation) in order to correct the issue, or do I need to start from scratch and split the database while it's on a Public drive.
I hope this makes sense. Thanks in advance for your help.
I just want to know that " How to split the Access database in Front End and Back End application"? I am creating a database that i want to store on server and simultaneously want to give access to 20 terminals (cleints) to access the database.
Secondly, I have to provide a field in a form "Document number". However as per the requirement user can enter "PIR No", "Serial No" or at times both as document number. Both the things "PIR No" and "Serial No" have different format types like "PIR No 001" and "Srl No001".
On basis of document number later i have to give the option to search the particular document. Please guide me how to provide the option to enter the field values.
I am almost at the finishing line with a great deal of help from here. I have now normalised the tables, built complicated queries, forms, reports, all from scratch as I knew absolutely nothing before I started with Access three months ago. I have compacted and repaired the database using the wizard, and also complied the code and analyzed all tables, forms, queries, and reports and relationships. The final step is to make it an MDE file so that it can go on the local network at work (not on the internet). My questions are these;
Do I need to split the database into front and back ends?
If I save a copy of the original MDB file and then make it a MDE file would that not suffice in making it run more efficiently?
Can a split MDB database be made into an MDE database?
I am combining 12 Databases. I have split all 12 between the server and the desktop. My question is “Should I combing all of the data table on the server into one database or should I leave all of the individual application data tables in separate Databases on the server”. Additionally, is there a limit to the number of tables an Access DB can handle? My inclination is to keep the functionality separated but the problem I have is that some of the functionality within the applications overlap. Recommendations!
The moment of truth finally came and I split my database FE/BE for testing only the truth was a bit sour.
Background: I have several forms in my database that have a common series of buttons at the top which open their corresponding form. Before the split, everything was fine - you can click on the button and the desired form would open. After the split, I'm getting the error message:
"Microsoft Office Access couldn't find the toolbar 'EVM Database Menu'."
This is referencing a toolbar that I used during development to help jump to forms.
I tried removing the toolbar from each form (Tools > Customize > Toolbars > unchecked the custom toolbar), and re-split the database FE/BE ends, but to no avail..
So, I checked the event codes to be sure I didn't program something wrong. There are 9 buttons total to open forms, 7 of them give this problem, the remaining 2 do not. The code for the problematic and non-problematic ones are identical!
Example - Non-Working (error message re: Custom Toolbar): ----------------------------------------------------------- Private Sub cmdActuals_Click() On Error GoTo Err_cmdActuals_Click
Dim stDocName As String Dim stLinkCriteria As String
Example - Working (no error message): ----------------------------------------------------------- Private Sub cmdPerfProj_Click() On Error GoTo Err_cmdPerfProj_Click
Dim stDocName As String Dim stLinkCriteria As String
Questions: So..this has nothing to do with code, it must be a problem in the linking somehow, right? A bug possibly? What else could be causing this? More importantly, is there a solution to my predicament that anyone could help out with? Searches so far have returned no help either from forums (including here), MS site (no Q-articles), and VBA Help. I'll continue searching though.
Hi, as an attempt to improve database performance, I have split a MS Access 2003 database. I have successfully split the database and saved the backend onto the server. My question is, where is the front end. or do I have to create it?
I have a call tracking database with 5 active users. Ocasionally the database will freeze, usually for several people at once. It will say: "Can not update record; Currently Locked"
The only way to fix it is to close and re-open. I split the database, compiled it and then created an MDE file to distribute. They are using copies of the front-end, not links. The database locking more and more every day. But we are using it more. After parusing the forum I'm starting to suspect that this is a problem of "Primary Key duplication" If everyone trys to create a record at the same time, would the database lock because we all created the same record at the same time?
If so, how do I get around this? Use something other than Autonumber for the primary key? Or is this an entirely different problem?
Hi all, I have noticed that ever since i split my database there is a considerable slow down of load time! When multiple users are on, it is also incredibly slow. is there a practice to follow to speed up the database? each user has their own front end, so im not sure if there is something else that can be done to speed it up
I am new to split database format... If I put the backend on say windows server 2000 or 2003 in a folder, is there anything else I need to do? Any setting on the server?? Or do I need a specific type of server os ie sql server etc?
