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
|
|||
|
|||
Potential Bug in Access 2007
I have noticed behavior in Access 2007 that could potentially delete/remove
relationships in your database when you try to split the database into a front end and a back end using the “Database Tools”-”Access Database” option. If you have a table locked (such as having the table open or a form (such as the switchboard) accessing a table) when you try and split the database you will get the following error “The database engine could not lock table ‘table_name’ because it is already in use by another person or process.” After clicking okay you will notice the split did not succeed because you still have all of your local tables and no linked tables. You will also notice all of your relationships defined in the database have been deleted. Now the back end is created correctly. The tables exist and the relationships are still defined. Now if you don’t realize your relationships have been deleted you might delete the back end (since it does not contain any of your custom objects, form, reports and so on) and try to redo the split after releasing the lock on your table. The problem is the split works but the back end is created without any relationships. I just thought I would share this in hopes that somebody could avoid losing their relationships. Always backup you database before doing a split. |
#2
|
|||
|
|||
Potential Bug in Access 2007
Following your steps, I ended up with a different result.
As you stated, the back end tables were created, but the attempt to create the relations in the back end failed because a form was open in the front end. Therefore the back end tables lacked the relationships. However, the front-end relations were still intact. So deleting the (incomplete) back end would not cause any grief. Tested in A2007 SP1. -- 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. "oracle8202" wrote in message ... I have noticed behavior in Access 2007 that could potentially delete/remove relationships in your database when you try to split the database into a front end and a back end using the “Database Tools”-”Access Database” option. If you have a table locked (such as having the table open or a form (such as the switchboard) accessing a table) when you try and split the database you will get the following error “The database engine could not lock table ‘table_name’ because it is already in use by another person or process.” After clicking okay you will notice the split did not succeed because you still have all of your local tables and no linked tables. You will also notice all of your relationships defined in the database have been deleted. Now the back end is created correctly. The tables exist and the relationships are still defined. Now if you don’t realize your relationships have been deleted you might delete the back end (since it does not contain any of your custom objects, form, reports and so on) and try to redo the split after releasing the lock on your table. The problem is the split works but the back end is created without any relationships. I just thought I would share this in hopes that somebody could avoid losing their relationships. Always backup you database before doing a split. |
#3
|
|||
|
|||
Potential Bug in Access 2007
That is strange. In mine the front end relationships are lost. I am also
using Access 2007 SP1. Microsoft Office Access 2007 (12.0.6211.1000) SP1 MSO (12.0.6320.5000) to be exact. "Allen Browne" wrote: Following your steps, I ended up with a different result. As you stated, the back end tables were created, but the attempt to create the relations in the back end failed because a form was open in the front end. Therefore the back end tables lacked the relationships. However, the front-end relations were still intact. So deleting the (incomplete) back end would not cause any grief. Tested in A2007 SP1. -- 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. "oracle8202" wrote in message ... I have noticed behavior in Access 2007 that could potentially delete/remove relationships in your database when you try to split the database into a front end and a back end using the “Database Tools”-”Access Database” option. If you have a table locked (such as having the table open or a form (such as the switchboard) accessing a table) when you try and split the database you will get the following error “The database engine could not lock table ‘table_name’ because it is already in use by another person or process.” After clicking okay you will notice the split did not succeed because you still have all of your local tables and no linked tables. You will also notice all of your relationships defined in the database have been deleted. Now the back end is created correctly. The tables exist and the relationships are still defined. Now if you don’t realize your relationships have been deleted you might delete the back end (since it does not contain any of your custom objects, form, reports and so on) and try to redo the split after releasing the lock on your table. The problem is the split works but the back end is created without any relationships. I just thought I would share this in hopes that somebody could avoid losing their relationships. Always backup you database before doing a split. |
#4
|
|||
|
|||
Potential Bug in Access 2007
You might try it with the switchboard form open. That is when I notice the
behavior on mine. Although I don't really see why this would make a difference other than it is not a table actually included in any of my relationships. "Allen Browne" wrote: Following your steps, I ended up with a different result. As you stated, the back end tables were created, but the attempt to create the relations in the back end failed because a form was open in the front end. Therefore the back end tables lacked the relationships. However, the front-end relations were still intact. So deleting the (incomplete) back end would not cause any grief. Tested in A2007 SP1. -- 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. "oracle8202" wrote in message ... I have noticed behavior in Access 2007 that could potentially delete/remove relationships in your database when you try to split the database into a front end and a back end using the “Database Tools”-”Access Database” option. If you have a table locked (such as having the table open or a form (such as the switchboard) accessing a table) when you try and split the database you will get the following error “The database engine could not lock table ‘table_name’ because it is already in use by another person or process.” After clicking okay you will notice the split did not succeed because you still have all of your local tables and no linked tables. You will also notice all of your relationships defined in the database have been deleted. Now the back end is created correctly. The tables exist and the relationships are still defined. Now if you don’t realize your relationships have been deleted you might delete the back end (since it does not contain any of your custom objects, form, reports and so on) and try to redo the split after releasing the lock on your table. The problem is the split works but the back end is created without any relationships. I just thought I would share this in hopes that somebody could avoid losing their relationships. Always backup you database before doing a split. |
Thread Tools | |
Display Modes | |
|
|