Split Database 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?
Thank you for taking the time to report an issue.
What's wrong... Please write below.
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?
Must it be on a shared network location in a Windows environment? Can it be placed on some FTP server?
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?
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?
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.
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?
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?
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.