Originally Posted by
maxhugen
I'm getting exactly the same error. I'm using MSCOMCTL.OCX.
My app started life ~15 years ago, and has progressed through A2000, A2003, and within the last 4 months, A2007 and now A2010.
I believe it's a corruption somewhere, presumably in the form itself. And it's not the first form that I've had corruption issues with since converting to A2007/A2010.
On my development machine, I received the error every time I opened the form. So I put a code break in the code that first calls the problem form (DoCmd.OpenForm "mwbsAssign"), and stepped through the code, trying to pinpoint where/how the error pops up. Lo and behold! The form opened AOK! So I removed the breaks, tried again, and now the form opens without error.
The app is delivered to clients on a server via TS, using an accde file. However, I also have the accdb file saved to the server as a backup, so I tried the same thing there, using RDP. Again, I put a break on the DoCmd.OpenForm code line, and started stepping through - but it did NOT step into the problem form's OnLoad event! This event calls a function which "loads" the ListView.
The form still opened, displayed the same error, and several columns in the list showed 'garbled' characters.
The fact that the list did show records indicates that the code to populate it DID run, yet neither the code breaks in the form's OnLoad or in the function it calls, stopped the code, nor did stepping through code step into that event or the function.
Conclusion: something in Access is definitely corrupt. I suspect the form itself.
How the form "fixed" itself on my dev machine when I stepped through code remains a mystery to me. It did not fix itself when I tried the same on the server.
In summary, the whole app seems unstable, with a number of forms seemingly corrupt etc. One by one I've sort of fixed them, but I think I'll try starting with a clean 2010 database, and import all the objects to it, and see if the issues remain.