|
| 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
August 26th, 2009, 03:52 AM
posted to microsoft.public.access
|
|||
|
|||
Access linked databases and Windows server 2008
I have 2 Access 2003 databases that are linked together. Each db has a table
linked to the other. (example: database 1 is linked to database 2 by one table and then database 2 is linked to database 1 by a different table). They worked fine running on a free standing computer with both db in the same directory. However when they were added to a server running Server 2008 they no longer do. When you opened one of the databases and relinked the table, the database doesn't want to shut down properly and hung the server. You then lose the share and crash the server. I did this twice today! I didn't make to many friends today to say the least when this happened! I have put the databases back on the free standing computer but that doesn't solve the problem. (After all why have a server if you can't put the data there.) Is the problem that there are 2 links? I can't test when there is no one in the office-I don't have access after hours. Any suggestions? I couldn't figure out a better place to post this question. Thanks for any advice 
|
|
#2
August 26th, 2009, 05:12 AM
posted to microsoft.public.access
|
|||
|
|||
|
Access linked databases and Windows server 2008
Only the data backend should be on the server. The front-end needs to be on
each workstation which accesses the data. Also make sure that you have permissions for everyone accessing the database back-end, including delete permissions so that the LDB file can be deleted. Change the way everything links. All links should be from the front-end to the back-end. Reciprocal links should not work. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com "jsrogol" wrote in message ... I have 2 Access 2003 databases that are linked together. Each db has a table linked to the other. (example: database 1 is linked to database 2 by one table and then database 2 is linked to database 1 by a different table). They worked fine running on a free standing computer with both db in the same directory. However when they were added to a server running Server 2008 they no longer do. When you opened one of the databases and relinked the table, the database doesn't want to shut down properly and hung the server. You then lose the share and crash the server. I did this twice today! I didn't make to many friends today to say the least when this happened! I have put the databases back on the free standing computer but that doesn't solve the problem. (After all why have a server if you can't put the data there.) Is the problem that there are 2 links? I can't test when there is no one in the office-I don't have access after hours. Any suggestions? I couldn't figure out a better place to post this question. Thanks for any advice
|
|
#3
August 27th, 2009, 02:11 AM
posted to microsoft.public.access
|
|||
|
|||
|
Access linked databases and Windows server 2008
Thanks I sort of figured that out. Will need to make a few changes to the
database. However the server crashed today and is no longer working (software issue-memory dumps and lockup!). I think that is a record-worked for 3 days. "Arvin Meyer [MVP]" wrote: Only the data backend should be on the server. The front-end needs to be on each workstation which accesses the data. Also make sure that you have permissions for everyone accessing the database back-end, including delete permissions so that the LDB file can be deleted. Change the way everything links. All links should be from the front-end to the back-end. Reciprocal links should not work. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com "jsrogol" wrote in message ... I have 2 Access 2003 databases that are linked together. Each db has a table linked to the other. (example: database 1 is linked to database 2 by one table and then database 2 is linked to database 1 by a different table). They worked fine running on a free standing computer with both db in the same directory. However when they were added to a server running Server 2008 they no longer do. When you opened one of the databases and relinked the table, the database doesn't want to shut down properly and hung the server. You then lose the share and crash the server. I did this twice today! I didn't make to many friends today to say the least when this happened! I have put the databases back on the free standing computer but that doesn't solve the problem. (After all why have a server if you can't put the data there.) Is the problem that there are 2 links? I can't test when there is no one in the office-I don't have access after hours. Any suggestions? I couldn't figure out a better place to post this question. Thanks for any advice
|
|
#4
August 27th, 2009, 11:55 AM
posted to microsoft.public.access
|
|||
|
|||
|
Access linked databases and Windows server 2008
Are you running MS-Office from the server? I've seen that work with Terminal
Services on Server 2003 and earlier, but I can't vouch for Server 2008. It seems to me that you have a server problem which may only coincidentally coincide with the Access problem. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com "jsrogol" wrote in message ... Thanks I sort of figured that out. Will need to make a few changes to the database. However the server crashed today and is no longer working (software issue-memory dumps and lockup!). I think that is a record-worked for 3 days. "Arvin Meyer [MVP]" wrote: Only the data backend should be on the server. The front-end needs to be on each workstation which accesses the data. Also make sure that you have permissions for everyone accessing the database back-end, including delete permissions so that the LDB file can be deleted. Change the way everything links. All links should be from the front-end to the back-end. Reciprocal links should not work. -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com "jsrogol" wrote in message ... I have 2 Access 2003 databases that are linked together. Each db has a table linked to the other. (example: database 1 is linked to database 2 by one table and then database 2 is linked to database 1 by a different table). They worked fine running on a free standing computer with both db in the same directory. However when they were added to a server running Server 2008 they no longer do. When you opened one of the databases and relinked the table, the database doesn't want to shut down properly and hung the server. You then lose the share and crash the server. I did this twice today! I didn't make to many friends today to say the least when this happened! I have put the databases back on the free standing computer but that doesn't solve the problem. (After all why have a server if you can't put the data there.) Is the problem that there are 2 links? I can't test when there is no one in the office-I don't have access after hours. Any suggestions? I couldn't figure out a better place to post this question. Thanks for any advice
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
