40 M mdb is not too big. Check your network. Is there a switch between server and hub? With or without switch will make big difference. Does NIC set to auto or full/half duplex in both server and workstation? As my experience, auto is fast. Also, try use pass through query in your application...
This case happened many times for me. Because the size of your MDB close to 2GB, there is no space to swap. Do the following steps:
1) from my computer, copy this MDB (A) to new MDB(B)
2) delete all tables in B
3) import one bigest table from A to B
4) compact B
5) check the size of B, repeat 3)...
Do you have backup? If yes, restore it. You can try scandisk disk. Sometime, try scan virus will help. But the simple way is to restore it from backup.
You need network administrator to change the setteing of network adapter. Before it, try just append a 100 records to SQL linked table. If still get time out error, I am sure that it is network performance problem. I have the same case.
This is very strange solution but work. You can find out on Microsoft web site.
Find and rename a font file called Hatten.ttf to Hatten.tt_. Re-install Access97. Rename the font file back.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.