If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Database Splitter
I am developing a comprehensive database for my company. I need to have our
employees start using a database to record time card activities ASAP. I'm considering splitting the database, placing the tables in a share located on our network. My understanding is that this will allow me to work on the forms, reports, etc., while users work with different beta versions of the front end on their systems. As my project develops I will probably have to make some changes to the tables and relationships on the back end? Could this be a problem. What if I needed to send you a copy of the database to help answer a question. Would I just send a copy of both files? If I needed to work on the project over the weekend on my laptop could I just copy both files and use the linked table manager to adjust for the new environment? Is this recommended? |
#2
|
|||
|
|||
Database Splitter
Yes, Steve, that approach is fine.
Modifying your copy of the front end is no issue. When you come to modify the back end, you will need everyone else logged out for that change. Unless you simulate the same path to the data on your laptop, you will need to reconnect the tables again after you change the location to the back end. If the Linked Table Manager proves inadequate, it's not difficult to pop up the FileOpen dialog, and then loop through the TableDefs, set the Connect property, and RefreshLink. The API call for FileOpen is he http://www.mvps.org/access/api/api0001.htm -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Steve" wrote in message ... I am developing a comprehensive database for my company. I need to have our employees start using a database to record time card activities ASAP. I'm considering splitting the database, placing the tables in a share located on our network. My understanding is that this will allow me to work on the forms, reports, etc., while users work with different beta versions of the front end on their systems. As my project develops I will probably have to make some changes to the tables and relationships on the back end? Could this be a problem. What if I needed to send you a copy of the database to help answer a question. Would I just send a copy of both files? If I needed to work on the project over the weekend on my laptop could I just copy both files and use the linked table manager to adjust for the new environment? Is this recommended? |
#3
|
|||
|
|||
Database Splitter
Thanks for your help. I'll get started then.
Steve "Allen Browne" wrote in message ... Yes, Steve, that approach is fine. Modifying your copy of the front end is no issue. When you come to modify the back end, you will need everyone else logged out for that change. Unless you simulate the same path to the data on your laptop, you will need to reconnect the tables again after you change the location to the back end. If the Linked Table Manager proves inadequate, it's not difficult to pop up the FileOpen dialog, and then loop through the TableDefs, set the Connect property, and RefreshLink. The API call for FileOpen is he http://www.mvps.org/access/api/api0001.htm -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Steve" wrote in message ... I am developing a comprehensive database for my company. I need to have our employees start using a database to record time card activities ASAP. I'm considering splitting the database, placing the tables in a share located on our network. My understanding is that this will allow me to work on the forms, reports, etc., while users work with different beta versions of the front end on their systems. As my project develops I will probably have to make some changes to the tables and relationships on the back end? Could this be a problem. What if I needed to send you a copy of the database to help answer a question. Would I just send a copy of both files? If I needed to work on the project over the weekend on my laptop could I just copy both files and use the linked table manager to adjust for the new environment? Is this recommended? |
Thread Tools | |
Display Modes | |
|
|