By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,928 Members | 1,456 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,928 IT Pros & Developers. It's quick & easy.

exclusively open, locking the database

P: n/a
Hi! Please help:
We have an Access application, using linked SQL server tables, on
network. After moving to a new server, the access file is always
crashed, sometimes the system table (Msysmodules2) exclusively opened
by another user (but the default open mode is Share), sometimes the
file is not recognized as Access file. Every time when that happened,
I have to copy the file from my C drive to the network to solve the
problem, but half day later, that happened again. The network people
don't think this is a server problem. What that could be?
Thanks!
Saiyou
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
One possibility is a faulty network card on the new server.
Access is more sensitive than other applications, so it can fail when other
applications seem to work fine.
Ask your network people to put a "sniffer" on the server's network card.

HTH
- Turtle

"Saiyou Anh" <wa***@alexian.net> wrote in message
news:a5**************************@posting.google.c om...
Hi! Please help:
We have an Access application, using linked SQL server tables, on
network. After moving to a new server, the access file is always
crashed, sometimes the system table (Msysmodules2) exclusively opened
by another user (but the default open mode is Share), sometimes the
file is not recognized as Access file. Every time when that happened,
I have to copy the file from my C drive to the network to solve the
problem, but half day later, that happened again. The network people
don't think this is a server problem. What that could be?
Thanks!
Saiyou

Nov 13 '05 #2

P: n/a

"Saiyou Anh" <wa***@alexian.net> wrote in message
news:a5**************************@posting.google.c om...
Hi! Please help:
We have an Access application, using linked SQL server tables, on
network. After moving to a new server, the access file is always
crashed, sometimes the system table (Msysmodules2) exclusively opened
by another user (but the default open mode is Share), sometimes the
file is not recognized as Access file. Every time when that happened,
I have to copy the file from my C drive to the network to solve the
problem, but half day later, that happened again. The network people
don't think this is a server problem. What that could be?
Thanks!
Saiyou


Is the Access file the Front-end? If so each user should have a private
copy.
Also, is the new sever a Windows server?
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.