Re: Form Dirty not firing
- From: "JB" <jenniferbanzon@xxxxxxxxx>
- Date: 22 Mar 2007 15:31:46 -0700
What is the best way to test for corruption and to correct it?
This application, I inherited it from another programmer, has been
very buggy and has crashed multiple times. I have not been able to
resolve many of the problems and they are on my "To Do" list. This is
a complex application with many forms, queries and tables in Access
XP. I need it to be stable for client delivery in two weeks and am
concerned that the errors and crashes I am dealing with may be related
to corruption but I want to be sure before I go down that path.
On Mar 22, 2:30 pm, "Mark A. Sam" <NotTell...@xxxxxxxxxxxxxxxxx>
wrote:
It does sound like corruption. Did you test it with another control besides
the first?
I would try creating a new DB, importting all of the objects into it then
try it. You could also make a new form and copy and paste the controls into
it a few at a time, testing the dirty property as you do it. The cause
could also be a corrupt control.
.
- Follow-Ups:
- Re: Form Dirty not firing
- From: John W . Vinson
- Re: Form Dirty not firing
- References:
- Form Dirty not firing
- From: JB
- Re: Form Dirty not firing
- From: Mark A. Sam
- Form Dirty not firing
- Prev by Date: Re: Go to Control with IIf statement
- Next by Date: Re: Go to Control with IIf statement
- Previous by thread: Re: Form Dirty not firing
- Next by thread: Re: Form Dirty not firing
- Index(es):