Network or Disk Errors in Access 1

[xtreme1]

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I'm unsure of the exact reason for this occurence, so I don't really know whether or not it relates to NT or to Microsoft Access.&nbsp;&nbsp;Occasionally, much more often than I'd like, one of the client machines will temporarily lose it's connection to the master .mdb file on the PDC.&nbsp;&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;We run, at the moment, a TCP/IP network that does not use DHCP.&nbsp;&nbsp;All addresses are static.&nbsp;&nbsp;Also temporarily, IPX/SPX is still used with the HP Jet Direct print servers on the network.&nbsp;&nbsp;All of the NIC's are Kingston 10/100.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The standardization of the NIC's, as well as the switch to TCP/IP were both done in an attempt to alleviate this problem.&nbsp;&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The error itself is displayed within MS Access, and after closing MS Access out on the clients machine that encountered the problem, you can usually start it right back up.&nbsp;&nbsp;No reboot necessary, nor a logout then log back in.&nbsp;&nbsp;For some reason it seems that the connection is just dropped, and then can be restablished.&nbsp;&nbsp;There are apporximately 20 computers altering this and a host of other network database files constantly, and what really bothers me about the situation is the following.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;About 30% of the time this occurs, the database file will need to be repaired.&nbsp;&nbsp;Anyone who's ever worked with Access will know that in order to repair the file, it cannot be in use.&nbsp;&nbsp;This results in me meandering about the office building asking people to please close out their database applications(keeping them out until it's repaired is actually the hardest part).&nbsp;&nbsp;If anyone has any suggestions, please post or just send me an e-mail.&nbsp;&nbsp;All responses will be appreciated.&nbsp;&nbsp;Thank you. <p>xtreme1<br><a href=mailto:rbio@excite.com>rbio@excite.com</a><br><a href= > </a><br>

 

[ATCal]

Does this happen randomly on various workstations, or isolated to one? <p>Al<br><a href=mailto: atc-computing@home.com> atc-computing@home.com</a><br><a href= > </a><br>

 

[xtreme1]

It happens on multiple machines, it doesn't seem to be isolated to any one.&nbsp;&nbsp;I wish it were, my life would be a whole lot simpler. <p>xtreme1<br><a href=mailto:rbio@excite.com>rbio@excite.com</a><br><a href= > </a><br>

 

[Vic88]

I had this problem once. It happened on only one machine. I changed the NIC and everything was fine. Maybe you should check the server's NIC<br><br><br><br>Vic88

 

[xtreme1]

Vic, it's definetely a possibility.&nbsp;&nbsp;Thanks, I think I will give that a shot. <p>xtreme1<br><a href=mailto:rbio@excite.com>rbio@excite.com</a><br><a href= > </a><br>

 

[Vic88]

Was the NIC the problem ?

 

[xtreme1]

Vic, yes it was.&nbsp;&nbsp;Multiple NICs actually, it's a complicated story...but you were correct.&nbsp;&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;It wasn't the servers NIC, it was a few of the client NICs that were causing problems, it was tough to determine which was the actual problem though.&nbsp;&nbsp;All of the machines causing problems were using Davicom NIC cards, just for all your information out there. =] <p>xtreme1<br><a href=mailto:rbio@excite.com>rbio@excite.com</a><br><a href= > </a><br>