Hey all,
I'm trying to finish up an Access DB for my employer but I am experiencing some debilitating problems this last week. For the record, the project is a chargeback recording, processing, reporting and analysis 'suite' in Access 2000.
After nearing completion of the project I started getting errors when I would try to access a few form's modules. It just seemed to get worse, but honestly I might have dug around more than usual after seeing the first and uncovered more problems in waiting.
The error I am consistently getting is "Error accessing file. Network connection may have been lost."
At first I just used a backup from the previous day and copied the form controls I had worked on from the bad copy. The problems started all over again and got increasingly more frequent. I struggled to find a reason for the errors and the closest I came was an MS KB that seemed to address my problem:
SYMPTOMS
When you try to view the code for a module, try to compile a database, try to create an MDE file, or try to execute code in a Microsoft Access 2000 database, you may receive one of the following error messages:
Error accessing file. Network connection may have been lost.
..................
CAUSE
You may receive one of these error messages when both Microsoft Access 2000 and version 6.3.91.8 of the Vbe6.dll file are installed on the computer, and either of the following conditions is true:
- You imported forms or reports that contain code modules or standalone modules into a new Microsoft Access 2000 database by using Microsoft Access 2000.
- You copied and pasted forms or reports that contain code modules or standalone modules into the Microsoft Access 2000 database by using Microsoft Access 2000.
Then, you close and reopen the database and try to view, execute, or compile the code.
I recently got a new computer here at work and it has the 6.3.91.8 version of vbe6.dll.
But this is what truly frustrates me. I spent my entire sunday afternoon rewriting the database from scratch at home. The only things I imported were .txt CSV files containing the old DB records (just a few table's worth). I didn't copy any forms or controls in an attempt to avoid catching this bug again.
I thought everything was OK, until this morning. The error is starting again in my DE form, which like the others I wrote over from scratch.
Can anyone guess why I am getting these errors? What might have caused them this time? I can't risk the integrity of this project over a stupid bug... I thought I had the answer but things aren't so clear now. I really need to know exactly what is causing this, so I never, ever see it again.
I'm on Win2K, the DB is not split, I have done repair/compact a number of times as well.
Any help or pointers would be invaluable. Thanks
I'm trying to finish up an Access DB for my employer but I am experiencing some debilitating problems this last week. For the record, the project is a chargeback recording, processing, reporting and analysis 'suite' in Access 2000.
After nearing completion of the project I started getting errors when I would try to access a few form's modules. It just seemed to get worse, but honestly I might have dug around more than usual after seeing the first and uncovered more problems in waiting.
The error I am consistently getting is "Error accessing file. Network connection may have been lost."
At first I just used a backup from the previous day and copied the form controls I had worked on from the bad copy. The problems started all over again and got increasingly more frequent. I struggled to find a reason for the errors and the closest I came was an MS KB that seemed to address my problem:
SYMPTOMS
When you try to view the code for a module, try to compile a database, try to create an MDE file, or try to execute code in a Microsoft Access 2000 database, you may receive one of the following error messages:
Error accessing file. Network connection may have been lost.
..................
CAUSE
You may receive one of these error messages when both Microsoft Access 2000 and version 6.3.91.8 of the Vbe6.dll file are installed on the computer, and either of the following conditions is true:
- You imported forms or reports that contain code modules or standalone modules into a new Microsoft Access 2000 database by using Microsoft Access 2000.
- You copied and pasted forms or reports that contain code modules or standalone modules into the Microsoft Access 2000 database by using Microsoft Access 2000.
Then, you close and reopen the database and try to view, execute, or compile the code.
I recently got a new computer here at work and it has the 6.3.91.8 version of vbe6.dll.
But this is what truly frustrates me. I spent my entire sunday afternoon rewriting the database from scratch at home. The only things I imported were .txt CSV files containing the old DB records (just a few table's worth). I didn't copy any forms or controls in an attempt to avoid catching this bug again.
I thought everything was OK, until this morning. The error is starting again in my DE form, which like the others I wrote over from scratch.
Can anyone guess why I am getting these errors? What might have caused them this time? I can't risk the integrity of this project over a stupid bug... I thought I had the answer but things aren't so clear now. I really need to know exactly what is causing this, so I never, ever see it again.
I'm on Win2K, the DB is not split, I have done repair/compact a number of times as well.
Any help or pointers would be invaluable. Thanks