Moving backend database

I have successfully split our database. In changing the location of the backend (_be) database (using a copy), then re-linking in the frontend (_fe) to the new _be location, there is no issue.

But if I rename the _be in the original location (which really should be deleted -- but glad I didn't yet), my front-end will not even come up (it shows the template page for newdatabases).

If I rename the _be database in the original location (which should not be involved anymore) to its correct name, the front end comes up, and tables show they are still correctly pointing to the new location.

I need to know how the original _be database from which I copied for the move, could have any relationship to my _fe pointing to the new location.

This is all I need to be complete my split, since I will be moving the split database off my pc into a server environment, now that I have installed Bob Larson's tool to enable auto-updates (a great piece of work).

Sponsored Links:

Related Topics

Got a problem with Moving into SQL
I have moved the backend of the database in SQL using the access wizard which seemed to work ok.

I have tried to link the frontend of the database onto the backend/SQL which I have followed the guide on MS (I hope is right ),

1st have I done it right by only moving the backend into SQL, 2nd when I have linked the frontend to the backend in SQL, I try to open one of the forms and it does not work, when I try and open the table in the frontend I get a message with says"ODBC - Call Failed" and when it opens it only has 63 recordes and not the 4500 which it should have and every field has #Name?

Reconnecting a split DB after moving one of the files?
I notice that if I move the backend database file, the front-end is unable to connect to it, and does not offer a prompt to locate the file. Is there any convenient way to help the front end DB relocate the backend DB file

Using Backend database to slow
I have a problem where the backend data is just way to slow to work with so I am trying to come up with a plan for working around it.

I was thinking about just copying the backend data to the users mydocuments folder and have the program access the data there but when changes were made then update the backend database.

Then update the local copy with the new id from the backend to the local version so the ID's and whatnot are controlled by the backend.

When the user opens the program after closing then it would just pull the backend data to the local machine again overwriting it.

I am grasping at straws here

Frontend Compact Backend
I have a database that is split and is set to make a backup copy of itself when it is started. This database loads multiple spreadsheets into a temporary table in the backend, summarizes the data via queries, and appends the summarized data to permanent tables.

Before the database is closed, I would like the user to be able to compact the backend of the database. Is itpossible to compact the backend of a database from the frontend? Or is this something that just needs to be done manually?

Location of backend database
I want to split my database into backend and frontend databases. I understand that the backend database needs to be placed in a shared location. I would like to know whether there are any restriction on the type of storage location for the backend database.

Must it be on a shared network location in a Windows environment? Can it be placed on some FTP server?

Frontend showing data, backend not updating
I have a very strange problem.

I have a backend-database on a network disk shared by 6 users. All users have a frontend client wich they use to administer the datebase. Everything in the frontend looks ok and they can query the latest data. However if I open up the backend database tables nothing has been updated since the middle of december. If I make a copy of the backend I can open it up and create new posts with ID-numbers that has already been taken by the frontend.

Ofcourse I have doublechecked that the clients are connected to the right backend file (there's only on backend file in the directory). Its all very strange and confusing, anyone with a good idea whats going on

Macro to load form not working after database split
Have a database that works just fine before running the database splitter. Once the database is split the macros to load a form will not run when you select the command button. It will only work for two users. These two users do have full control of the folder where the database frontend and backend are stored. I did give certain users and groups full control as well but the macros will still not load the form.
No error messages are displayed. I did update the links but it did not make a difference.
Both the frontend and backend are located on the server but I also tried moving the frontend to the local computer and it did not make a difference

duplicating backend
I am modifying the existing database.
I today created a copy of both front and back end.
When I made changes in the copy of backend table definition,
They also reflected in the database in use.

Could someone please help with creating a duplicate backend where
I should be able to make changes without effecting the actual database in use and also test the changes using the front end.

How to show data in Access Form
I have created Access database as a frontend application and another database as a Backend Database (all the databases are password protected). All tables and queries are stored in Backend Database.

My problem is that I need to create a form (Combo filters) with sub-form (List of the columns). I don't know how to show the data in this form / sub-form from backend database,

backend and links questions
with the below.

I have a split database, with the backend saved on a network.

1) How can I retrieve the name and location of the backend in VBA?
2) Is it possible to change the linked location for each table via VBA, say for example if I wanted to switch the tables to point to a backup version of the backend, or if a user had different drive mapping on a there machine which meant that the table location had to be remapped

Protecting backend table data
I split a database and password protected the backend and relinked them to the front end of the database. After learning that access stores the backend pw after it has been entered I've been trying to find a way to protect the table data.

Is there a way to make the tables read only? or make users re-enter the backend pw everytime they try to access the tables?

PS Why did the program dev's set up '07 like that?! I'm so confused Why pw protect a backend if access just stores it

SQL Server Backend is Read Only
I have upsized my access program backed to SQL Server Express 2008 using the SQL Server Migration Assistant. Everything seems to be working fine in query mode only. That is, my Access program can access the data in the database. However, if I try to do an Update or Add Record. I get an error message that the Backend SQL Server Database is Read-Only.

I looked at the Backend database from SQL Server Management Studio and ReadOnly is set to False.

It looks like the problem may be the way I linked the Backend or the way Access opens the SQL connect.

Any ideas what I need to do to make Access 2007 access the SQL Server Express backend database not in a ReadOnly mode?

Moving All Data from one Database to Another
I need to replace the backend of my database with one that adds several fields to many different tables. There are currently 122 tables so the manual method is not very appealing (especially because I anticipate further additions from the client which would require me to do it again). The database is currently live so I need to transfer all the data from the existing database into the tables of the new database. I am not on site so I will be sending the client an update so I need to do it via code. How do I cylce through all of my tables and Insert all the data from my tables in one database to another? One more element is having the user that will actually perform the update point to the existing database location through a browse window

Linking frontend access into SQL database
I have a access 2010. Database which I split into frontend and backend which works well.

I have decided to move the database into SQL, I used the export wizard and moved the database into SQL which seemed to work, and it I look at the backend which SQL made I seem to see mydata, and if I open SQL it seems to be in that to.

But my problem is, how do I link the access frontend to the SQL backend.

Linked Tables Twice?
Currently we have an access 2000 backend database with front ends on access 2003 and 2007. I am looking at creating a database which references some of the tables in the original backend.

Rather than risk disturbing this database I was considering creating another backend database with the original tables linked to the new backend. Then the front ends would link to the new back end and by association, the linked tables in the old back end. Will this work or is it just plain nuts/bad practice?

Unsecured Backend
I am using Access 2007. I have developed a database that will be used in a workgroup environment by 3-4 computers. I will have no access to this network. All the PCs on this network uses Access 2007.

The database will be placed in a shared folder on one of the PCs. I will need to split the database. But because I am not on this network and can not connect to this sharedfolder, how can I split the database on my computer with the proper Network Path of the shared folder and then give them a copy of the backend and front end instead of giving them thedatabase as is and then guide them to split it?

Also, the users will have to have Read/Write access to this folder in order to used the backend of the database. I can convert the frontend to ACCDE, but not the backend. If the users can connect to this folder with Read/Write access, they will have access to an unsecured backend.

Unless I don't know any better, how does this splitting provide and security for the data?

I don't understand this error message
I can open the backend database in access 2007, I can open the linked table in the front end database. The backend database has a single table in it and the table is empty. I have repaired and compacted the backend db several times. I can't run an append query to the linked table, as I get the following error message:

Cannot open database ". It may not be an application that your database recognizes, or the file may be corrupt.

Huh? is there something I am missing

Multiple connections to a single backend
I have split my database and have the front end on numerous PC's. Is this the preferred method of a multi user database? The reason I ask is not all the data is making to the backend - only some records.

update imported table like a refresh
I have an access database as a backend to store my data. We use a visual basic front end. I would like to use the data in the backend in another smaller access database. I know i can link the tables from one to another. But if i do this i can't add anything in the other smaller database as they are only linked. If i import the table to another smaller database i can add more data and fields however i can't update the data from the original database (backend) to the imported table. Is there a way that i can update the data from the backend database to the imported table, like a refresh would do if you have an excel query running i guess.

When I change backend password.Frontend wont open
I have a passed down access 2003 database. That if I change the backend password. I get an error message that the previous owner set up. But I'm new to programming and can't fiqure this out. I cant leave the database with the old password because other users that have left the dept have this old pw and thus have access to my backend