Related Topics

Split Database Backend

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?


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 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?


Split Database on CD
I've been asked to provide a copy of a database to an external client. The database is split, with the backend normally residing on the server and each user having a front end.

I'm assuming my client won't have the Access knowledge to relink the tables, so how do I link them to the backend, which will be on the CD, before I even burn the CD?


Split db and have backend on local PC
I want to split my db for other reason than to share with tons of people and I need the backend on the local machine with the front end but in a different directory. The db front and backend will be
distributed as a packaged solution to a singler user. The user will install the access runtime as well as the db's.
When I try to split the db called My Jewelry Project and place the backend in a folder called My Jewelry Data using this address //My Document/My Jewelry Data/JeweryData.accdb
it will not find the location.even though the folder exists.

I've tried ~/bla bla bla | and ~//bla bla bla and these links do not work either.

So how do I split a db and have the backend on the same computer with a relative path?


Problems accessing a split database
I have successfully split my database (frontend/backend) and have the backend stored on a sharepoint for my team to use. One thing I noticed we all had to do is map the same drive letter to the network path where the backend is stored. Since I initally split the db on my pc using drive W, the db now requires everyone else to use the same drive letter.

So everyone maps a W drive for the path where the backend resides, and has a local copy of the front end. 3 of us can pull it up fine and we can have multiple instances running with no problems. One user however, gets the error: "W:\ is not a valid path. Make sure the path name is spelled correctly and that you are connected to the server on which the file resides." I have verified that this user does indeed have drive W mapped to the correct location, but he still gets the error.


Adding tables to a split database
I am calling for a little help once again. I have recently spit my database I guess you would say successfully haha. I am trying to add another table to the database. I thought it would be straight forward, just open the backend database and add the table. The problem I came across is that I need one of the fields to be a lookup field from a query. With the database being split, the queries are on the front end, and the tables are on the backend. I'm sure there is a way to pull this off, but my rookie skills are lost once the wizard turns up blank


Problems accessing a split database
I have successfully split my database (frontend/backend) and have the backend stored on a sharepoint for my team to use. One thing I noticed we all had to do is map the same drive letter to the network path where the backend is stored.

Since I initally split the db on my pc using drive W, the db now requires everyone else to use the same drive letter.

So everyone maps a W drive for the path where the backend resides, and has a local copy of the front end. 3 of us can pull it up fine and we can have multiple instances running with no problems.

One user however, gets the error: "W:\ is not a valid path. Make sure the path name is spelled correctly and that you are connected to the server on which the file resides." I have verified that this user does indeed have drive W mapped to the correct location, but he still gets the error. I'm lost.any takers?


Splitting Access 2010
I am trying to split an Access 2010 database. The database currently has a switchboard. Problem is each time I try to split the database I get an error message saying that the database splitter cannot convert the switchboard or something to that effect. I do see the database saved in the location that I selected for the backend but it is not split because It contains all the tables, forms and queries created prior to splitting. Do I need to get rid of the switch to enable Access to split the database? Has anyone had this particular problem with Acccess 2010 and is there a way to split the database given what I have just naratted


Split Database Workaround - Connecting to BE and Dumping Data?
I have a split database that has a backend that resides on a server for my company. People in one building can access everything just fine with no speed issues, however the building Ireside in does not have the privileges having updated networking.

Looking for workarounds. Working locally will be the best option. Is it possible to connect the database's front end with the backend at startup, import all of the data from the server into my tables, and then close the connection again? On the front end, I plan to have a button that syncs data by connecting to the backend, updating the tables with any changes, and disconnecting.


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


Trouble with split database
I added a new table to my frontend database, forgetting that it was split. I then copied the table into my backend database and tried to use the Linked Table Manager to refresh the links. I've had trouble with the Linked Table Manager before, as it never seems to work as expected.

I was never able to get the tables linked, so eventually the only thing I could see to do was try resplitting the database using the Wizard. After all, This worked really smoothly, except it apparently allowed me to effortlessly wipe out all the data in my backend database. If nothing else, I want to post a warning to others that this thing is a menace.

My next step was to restore my backend from yesterday's backup by copying it over the old corrupted backend, and using the Linked Table Manager to refresh the links. Maybe it wasn't necessary to refresh the links, but my applications seems to be working again.

I still don't know how to add the new table to my backend database. This is another subject not addressed in any of my reference books. And now, the table is missing from the frontend too, though it is still listed as an object. When I try to open it, I get the error message that the Access db engine cannot find the input table.


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.


split database on web
I was wondering if it was possible to split a database and have the backend on a website of some sort, so each time a Front end is opened it reads from the internet and not something like a sharepoint.


Cant see any record in the main database
i have a very simple database wid one table & around 30 attributes. i linked the forms, queries & reports to it. In the end i split the database into frontend & backend. Backend is on the shared folder & frontend is distributed to all the users on their desktop.

now i want to ask that whether the records saved from the frontend of the users should get saved in the main file???? because i can see the records in the table of frontend & backend but not in the main file (which was split)


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


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.


Split DB - Front and Backend
I have no experience of network db and deploying it on the server.

1. When I wish to split a db where on which computer in LAN should I start splitting it from - Server or Client?
2. Complete steps of after split db.
3. Can a DB which is split in a standalone system as 'DB' and 'DB_be' be deployed in LAN with backend on server and the others on different clients.
4. Should the linked tables be moved to server from client if it is split from client by Link Manager.

What other steps are needed in successful deploy and test of DB? Can you give complete picture of the process with the help of screenshots in an actual C/S environ?


Access 2007: Working With Linked Tables
I have an application written in Access 2007 using VBA and sitting on an accdb database. Following good practice I've split the database to separate the code/forms/reports/queries (front end) from the data (back end). One of the objectives of this was to make maintenance easier.

However I've just developed an enhancement to the application which requires a new table. So in my development environment I've created the new table in my front end accdb. Now I'm happy that is working ok I want to move the data in this table to the backend and point the front end to the back end.

Using the options Access offers I cannot find a way of easily doing this.If I use the Linked Table Manager the new table does not appear in the dialog.

In the end I have managed to do it by:
1 - Deleting tables from my Front End database apart from the new one. 2 - Copying all tables from the backend database to the front end and having to confirm for each one that I want to copy both structure and data.
3 - Delete the backend database
4 - Split the database again, recreating the backend db by linking tables (including the new one) to it.

This approach seems long winded and prone to error. Did Microsoft design it to handle such a situation in this way or am I misunderstanding how to do this?

I guess what I'm asking is what is the recommended way of creating new tables in a database that has already been split.


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).