By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,393 Members | 1,405 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,393 IT Pros & Developers. It's quick & easy.

Corrupted form/control

P: n/a
I posted the other day that the Incremental Search box that I had been using
was no longer working properly. When I checked the code against an older
version that was working properly, the changes to the code from the old
(good) to the new (bad) version were minor and seemed unlikely to be the
cause of a problem. I then changed them one-at-a-time back to the old
version. Finally, the code blocks seemed identical. Just to be sure, I
copied all of the code from the good form to the bad form and the bad form
still did not work.

But then I copied the ListBox control itself from the good form to the bad
form and then the bad form suddenly worked fine. IOW, I had a corrupted
control.

Q: Is there a better way to test for a corrupted control than to pound
your head against a wall for a few days, some testing procedure, some
checksum value, anything?

Q: Even though things are working now, is it likely that the form itself is
corrupted and that the control will become unstable again?

Q: What, if anything, should I do now?

Thanks
CA
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Good troubleshooting.

Based on our experiences, there are several things you can do to prevent the
corruption recurring. We listed them in this article:
Preventing corruption
at:
http://allenbrowne.com/ser-25.html
The first 4 items are the most crucial.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Colleyville Alan" <ae***********@nospam.comcast.net> wrote in message
news:wKMEc.7900$%_6.4186@attbi_s01...
I posted the other day that the Incremental Search box that I had been using was no longer working properly. When I checked the code against an older
version that was working properly, the changes to the code from the old
(good) to the new (bad) version were minor and seemed unlikely to be the
cause of a problem. I then changed them one-at-a-time back to the old
version. Finally, the code blocks seemed identical. Just to be sure, I
copied all of the code from the good form to the bad form and the bad form
still did not work.

But then I copied the ListBox control itself from the good form to the bad
form and then the bad form suddenly worked fine. IOW, I had a corrupted
control.

Q: Is there a better way to test for a corrupted control than to pound
your head against a wall for a few days, some testing procedure, some
checksum value, anything?

Q: Even though things are working now, is it likely that the form itself is corrupted and that the control will become unstable again?

Q: What, if anything, should I do now?

Nov 13 '05 #2

P: n/a
Thanks for the info.

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:40***********************@per-qv1-newsreader-01.iinet.net.au...
Good troubleshooting.

Based on our experiences, there are several things you can do to prevent the corruption recurring. We listed them in this article:
Preventing corruption
at:
http://allenbrowne.com/ser-25.html
The first 4 items are the most crucial.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Colleyville Alan" <ae***********@nospam.comcast.net> wrote in message
news:wKMEc.7900$%_6.4186@attbi_s01...
I posted the other day that the Incremental Search box that I had been

using
was no longer working properly. When I checked the code against an older version that was working properly, the changes to the code from the old
(good) to the new (bad) version were minor and seemed unlikely to be the
cause of a problem. I then changed them one-at-a-time back to the old
version. Finally, the code blocks seemed identical. Just to be sure, I
copied all of the code from the good form to the bad form and the bad form still did not work.

But then I copied the ListBox control itself from the good form to the bad form and then the bad form suddenly worked fine. IOW, I had a corrupted
control.

Q: Is there a better way to test for a corrupted control than to pound
your head against a wall for a few days, some testing procedure, some
checksum value, anything?

Q: Even though things are working now, is it likely that the form itself

is
corrupted and that the control will become unstable again?

Q: What, if anything, should I do now?


Nov 13 '05 #3

P: n/a
Thanks for the info.

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:40***********************@per-qv1-newsreader-01.iinet.net.au...
Good troubleshooting.

Based on our experiences, there are several things you can do to prevent the corruption recurring. We listed them in this article:
Preventing corruption
at:
http://allenbrowne.com/ser-25.html
The first 4 items are the most crucial.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Colleyville Alan" <ae***********@nospam.comcast.net> wrote in message
news:wKMEc.7900$%_6.4186@attbi_s01...
I posted the other day that the Incremental Search box that I had been

using
was no longer working properly. When I checked the code against an older version that was working properly, the changes to the code from the old
(good) to the new (bad) version were minor and seemed unlikely to be the
cause of a problem. I then changed them one-at-a-time back to the old
version. Finally, the code blocks seemed identical. Just to be sure, I
copied all of the code from the good form to the bad form and the bad form still did not work.

But then I copied the ListBox control itself from the good form to the bad form and then the bad form suddenly worked fine. IOW, I had a corrupted
control.

Q: Is there a better way to test for a corrupted control than to pound
your head against a wall for a few days, some testing procedure, some
checksum value, anything?

Q: Even though things are working now, is it likely that the form itself

is
corrupted and that the control will become unstable again?

Q: What, if anything, should I do now?


Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.