I am trying to split another database, and after I name the backend, I get an error "The database engine could not lock table "switchboard items" because it is already in use by another person or process". I'm using access 2000 on windows 2000 os. Anyone have any idea what went wrong?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
database splitter error
- Thread starter Goyo1
- Start date
I'm not sure what's causing the problem, but it sounds to me as if you moved the Switchboard Items table to the back end. That's not a good idea; you should leave it in the front end.
Switchboard Items isn't your users' data, and your users will never see it, let alone update it. All it is is control information for the user interface. It never gets updated during multiuser use, so there's no need to share it, and since it's only UI information, it should stay with the front end with the other UI elements (forms, reports, etc.). That way it loads locally, instead of over the network.
The exception to this rule would be if you want to store Switchboard Items in the back end so that any changes you make to it will automatically become active in all your user's front ends without you having to get all the front ends updated. If that is the case, your question above still applies. The only thing I can think of that might be causing the problem is if the switchboard form is open at the time (perhaps hidden?). It should be closed while you're doing the split.
Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
Switchboard Items isn't your users' data, and your users will never see it, let alone update it. All it is is control information for the user interface. It never gets updated during multiuser use, so there's no need to share it, and since it's only UI information, it should stay with the front end with the other UI elements (forms, reports, etc.). That way it loads locally, instead of over the network.
The exception to this rule would be if you want to store Switchboard Items in the back end so that any changes you make to it will automatically become active in all your user's front ends without you having to get all the front ends updated. If that is the case, your question above still applies. The only thing I can think of that might be causing the problem is if the switchboard form is open at the time (perhaps hidden?). It should be closed while you're doing the split.
Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
- Thread starter
- #3
Appreciate the response here. But a question, how did the switchboard items get into the back end, or how do I get it out? I'm just trying to split a database for the first time. Not knowing exactly what I'm doing, but I do now show a backend named file. But I'm not sure if it works (since the original full database is still there).
How can I tell if it's split or not. Shouldn't the new front end asked to be named too?
How can I tell if it's split or not. Shouldn't the new front end asked to be named too?
Ah! I didn't realize you were using the Database Splitter.
All the DB Splitter does is create a new back end database, move the tables to it, and then link the tables into the original database. I personally don't think the Splitter wizard should move the Switchboard Items table, but it doesn't make an exception.
The wizard doesn't create a new front end file, it just modifies the original database to be a front end. I think the splitter probably ran correctly for you. It looks almost the same to you, but there should be one difference: the tables in the Tables page of the Database Window should now be links, with their icons having an arrow next to them.
If that's what you have, the error message you got was spurious, and you can ignore it if it doesn't keep happening. However, you should move the Switchboard Items table back to the front end. Proceed as follows:
1. Open the front end (your original db). If the switchboard form opens, close it.
2. In the Tables page of the Database Window, delete the link to Switchboard Items.
3. Choose File | Import. Find the back end database and select the Switchboard Items table. Click OK. The table will be copied back to the Database Window.
4. Close the front end database and open the back end database.
5. In the Tables page of the Database Window, delete the Switchboard Items table.
If your original database doesn't now have table links for all tables (as shown by the icons with arrows), tell me what you have on the Tables page.
Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
All the DB Splitter does is create a new back end database, move the tables to it, and then link the tables into the original database. I personally don't think the Splitter wizard should move the Switchboard Items table, but it doesn't make an exception.
The wizard doesn't create a new front end file, it just modifies the original database to be a front end. I think the splitter probably ran correctly for you. It looks almost the same to you, but there should be one difference: the tables in the Tables page of the Database Window should now be links, with their icons having an arrow next to them.
If that's what you have, the error message you got was spurious, and you can ignore it if it doesn't keep happening. However, you should move the Switchboard Items table back to the front end. Proceed as follows:
1. Open the front end (your original db). If the switchboard form opens, close it.
2. In the Tables page of the Database Window, delete the link to Switchboard Items.
3. Choose File | Import. Find the back end database and select the Switchboard Items table. Click OK. The table will be copied back to the Database Window.
4. Close the front end database and open the back end database.
5. In the Tables page of the Database Window, delete the Switchboard Items table.
If your original database doesn't now have table links for all tables (as shown by the icons with arrows), tell me what you have on the Tables page.
Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
- Thread starter
- #5
Well, Rick, again, thanks for responding. For the record, it has me as Goyo1 (spanish for Greg), then says programmer. I hope you can already tell that I'm a little bit overrated! I'm just dangerous enough to...be dangerous!
I opened up the front end, and the switchboard opened. I closed it, but didn't see how to delete the link to switchboard. So I did delete the newly made backend and started over with a new split. It worked, and I didn't see the switchboard error.
However, looking at the tables in the backend, it only has 3, agency profile (this is an insurance client database, but this table holds info on the agency itself), switchboard items, and zipcodes (have all the zipcodes from everywhere). Thats it.
Looking at my current database (took that one and stripped it down to this new one), I see many more tables there. So again, I don't know if it split it or not.
I opened up the front end, and the switchboard opened. I closed it, but didn't see how to delete the link to switchboard. So I did delete the newly made backend and started over with a new split. It worked, and I didn't see the switchboard error.
However, looking at the tables in the backend, it only has 3, agency profile (this is an insurance client database, but this table holds info on the agency itself), switchboard items, and zipcodes (have all the zipcodes from everywhere). Thats it.
Looking at my current database (took that one and stripped it down to this new one), I see many more tables there. So again, I don't know if it split it or not.
I'm not sure I understand what's going on. You didn't develop this database? Has it been assigned to you for maintenance?
You refer to at least 3 databases--current database, that one, new one, original db--with varying numbers of tables and/or links, but I'm totally confused about which reference refers to what. It sounds as if some tables may have been marked Hidden.
Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
You refer to at least 3 databases--current database, that one, new one, original db--with varying numbers of tables and/or links, but I'm totally confused about which reference refers to what. It sounds as if some tables may have been marked Hidden.
Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
- Status
Similar threads
