Error 3043 Disk or Network Error

[Yelena Varshal via AccessMonster.com]

Hello,

One of my 500 users gets an error when starting MS ACCESS application that
uses DAO to connect to another database in the same folder.
Error 3043 Disk or Network Error
The application closes after he clicks OK on the message and his computer
freezes and needs to be rebooted. He is a remote user so I have no access to
his machine, only can ask him to check things.

I did a research on the subject and found several reasons:
- network drive is not available - not relevant here
- several apps access the database at the same time - not relevant here
- TEMP directory for a user (under Local Settings) is missing or TEMP and TMP
variables point to non-existiung directory - let the user know to check that
- not sufficient space on the computer - let the user know to check that
- no Write access to TEMP directory - let the user know to check that
This person does have low available memory on his Windows 2000 workstation,
told him to check Task Manager Processes to see where does memory go. This
may be consistent with computer freezing.

Any other ideas or maybe some experience with the issue?
We do know that the error takes place in a specific procedure that consists
of several lines of code that connect another DB using QueryDef object. We
also know that the second database is getting connected (somehow?) because
the error handler for these several lines of code does log a custom error in
a custom table in this second database.

Thanks in advance,
Yelena