M
Mike Thomas
In Access 2000 running on WIndows XP, I am running into a very time
consuming problem receiving the error message "Error Accessing File.
Network Connection May Have Been Lost." I have to make a new mdb, copy in
all of the objects, redo whatever work has been lost, etc. The problem
usually involves the VB code files behind a form.
I think this error message is a euphamism for file corruption - it this
correct? My development computer is not even on a network.
The setup of the app is as follows: the front end and back end are
separated. I have been writing this for one client since 1998, and the
front end is now about 16 meg, the back end about 100 meg, but so far no
problems with the back end.
- Is the front end considered large by Access standards? Could it be too
large? (I've been trying to get this client out of Access anyway almost
since this project began)
- One symptom of the corruption seems to be Access losing control over the
VB code behind files, some of which can run to 20 or so pages. (I'll open a
form, then look at the code and realize that the code belongs to a different
form or module. Would it be helpful to move the code away from the forms
and into the stand alone modules?
- Other than decompile, compile, and compact & repair,. is there any way to
truly clean up an mdb? I think there is a problem with 'shadow code'. Eg
code which is still in the mdb, but it cannot be seen. Sometimes the app
seems to revert to using old code long since deleted, but I cannot find it.
When I load the next app, the behaviour goes away, only to show up a couple
of weeks later.
- Does anyone know of a good site dealing with Access file corruption? It
has gotten to the point where it is getting hard to work on this project.
Many thanks,
Mike Thomas
consuming problem receiving the error message "Error Accessing File.
Network Connection May Have Been Lost." I have to make a new mdb, copy in
all of the objects, redo whatever work has been lost, etc. The problem
usually involves the VB code files behind a form.
I think this error message is a euphamism for file corruption - it this
correct? My development computer is not even on a network.
The setup of the app is as follows: the front end and back end are
separated. I have been writing this for one client since 1998, and the
front end is now about 16 meg, the back end about 100 meg, but so far no
problems with the back end.
- Is the front end considered large by Access standards? Could it be too
large? (I've been trying to get this client out of Access anyway almost
since this project began)
- One symptom of the corruption seems to be Access losing control over the
VB code behind files, some of which can run to 20 or so pages. (I'll open a
form, then look at the code and realize that the code belongs to a different
form or module. Would it be helpful to move the code away from the forms
and into the stand alone modules?
- Other than decompile, compile, and compact & repair,. is there any way to
truly clean up an mdb? I think there is a problem with 'shadow code'. Eg
code which is still in the mdb, but it cannot be seen. Sometimes the app
seems to revert to using old code long since deleted, but I cannot find it.
When I load the next app, the behaviour goes away, only to show up a couple
of weeks later.
- Does anyone know of a good site dealing with Access file corruption? It
has gotten to the point where it is getting hard to work on this project.
Many thanks,
Mike Thomas