T
Tony Toews
sassycat8 said:Finally, there is resolution. I reistalled Access and disconnected the second
hard drive, to no avail. I got my database to work normally on another
computer, which meant to me that something was wrong on the hardware
end.
Agreed.
I had forgotten that the new hard drive had not worked with the old
controller, so my hard drives were moved to a new yet identical machine. (The
IT department handles all of that stuff, I might have been more prone to
think about it had I actually done it.) So I finally convinced them to wipe
my computer and start over, and Access has returned to normal funtionality.
My databases on the second drive ar fine.I don't think I will ever know what
happened. My hard drive was extremely fragmented, and wouldn't defragment.
There was a ton of stuff in the temp file, as you suggested. Maybe all of
these things combined?
No, I would say there was a hardware problem with your second hard
drive and such.
The truly happy ending is that I found out I can use a SQLserver that is on
site. My boss was under the impression that we didn't have a license for it,
and I felt my project did not warrant the giant expense.I tried to use
SQLserver express, but my data was to big for it. I think that the move to
SQLserver as a backend may be worth all of this headache.
I really appreciate all of your time. Your suggestions kept me moving forward.
Fabulous. Yes, given that your MDBs are at 2 Gb then I'd agree that
going to SQL Server is your best solution. However they might not
like your consuming 98% of the resources for an extended period of
time as you run your queries. <smile>
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm