Topics Search

Split Database Backend

Split Database Backend
Views: 12
So sometimes it is hard to do a compact and repair of the backend because their always seems to be users in the database (ie there is a Record Locking File of the backend).

1 - Is there a way to force everyone out of the database?

2 - What would happen if I copied the backend to a different location, and then pasted it back after I did the compact repair. This makes me nervous because the record locking file is there and wont let me delete it. So not sure if the copy and past of the backend will affect that file?
Sponsored Links:

More topics

 

Unsecured Backend

Preview
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

Preview
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

Preview
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

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

Problems accessing a split database

Preview
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

Preview
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
 

Split db and have backend on local PC

Preview
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

Preview
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

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

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