First of all I would like to thank everyone here who has helped me through my time creating this database. Without you guys I would not have a database to deploy. It is a pretty simple thing right now and will only be installed on 3 other machines running the 2007 runtime version (my station being the 4th but the only one with full Access 2007). I am finally ready to deploy it in my office and have some questions on how to.
I want to split it into front end and back end files and obviously install the front end on each machine and will plan on keeping the back end file on my machine (we do not have any type of technical server in our network, just 4 machines networked through basic microsoft networking). Splitting the file is no problem, I figured out how to do that just fine. My question is how do I "link" the tables in the front end copies to the tables in the back end that are now over the network, using the runtime version?
For example...
My original file (before split) was in the My Documents folder on my workstation. I split the file and saved the Back End file in the C:\Shared data directory (which is a shared folder on my computer). Now if I open the front end file (still in My Documents), all the tables are now "linked" to the file C:\Shared Data\My database_BE.accdb. Opening the front end file on my system works fine. But now when I copy a front end file to another system, the "linked tables" to the back end file are looking for the directory C:\Shared Data...., when in reality the directory would now be 192.168.1.104\Shared Data...... The runtime version of access does not seem to let me re-link (or update location of) the back end tables. How would I go about setting this up so each workstation is linked to the back end file on my computer?
I also noticed in the runtime version, the Ribbon is gone and also the navigation pane (displaying tables, forms, queries etc.) is gone. Obviously the runtime version blocks out development features, so i can understand lots of stuff "missing", but how would you open forms and such without that pane? (This is just a question for reference though, my DB does already have a navigational form I created where I would never need that pane to open objects, I was just wondering though)
I want to split it into front end and back end files and obviously install the front end on each machine and will plan on keeping the back end file on my machine (we do not have any type of technical server in our network, just 4 machines networked through basic microsoft networking). Splitting the file is no problem, I figured out how to do that just fine. My question is how do I "link" the tables in the front end copies to the tables in the back end that are now over the network, using the runtime version?
For example...
My original file (before split) was in the My Documents folder on my workstation. I split the file and saved the Back End file in the C:\Shared data directory (which is a shared folder on my computer). Now if I open the front end file (still in My Documents), all the tables are now "linked" to the file C:\Shared Data\My database_BE.accdb. Opening the front end file on my system works fine. But now when I copy a front end file to another system, the "linked tables" to the back end file are looking for the directory C:\Shared Data...., when in reality the directory would now be 192.168.1.104\Shared Data...... The runtime version of access does not seem to let me re-link (or update location of) the back end tables. How would I go about setting this up so each workstation is linked to the back end file on my computer?
I also noticed in the runtime version, the Ribbon is gone and also the navigation pane (displaying tables, forms, queries etc.) is gone. Obviously the runtime version blocks out development features, so i can understand lots of stuff "missing", but how would you open forms and such without that pane? (This is just a question for reference though, my DB does already have a navigational form I created where I would never need that pane to open objects, I was just wondering though)