Hi Barbara,

After spending all afternoon figuring out what it WASN'T..and lots of the usual checks...LOL..I found that the newly converted table had "something" to do with it. I deleted it, and copied it back - and after conversion and rebuilding the class, everything was fine. As near as I could tell, it was an issue related to changing what was a logical field into a character field. The second time around, I just deleted the logical field and inserted a new C field.

Anyway....its working again and the masses can now go boldly where only I have gone thus far! *g*

Thanks :)

>Phil, will the VCX work with your original test table? Since it was a copy, presumably you can test it out again. Also, have you tried the usual checks: Database validates with the new table in it? VCX was packed? DBC was packed? New table has the identical structure, etc.
>
>HTH
>Barbara
>
>>Help!
>>
>>I had a form class (part of a larger vcx) that was working fine all morning. As I finally finished the work on this module, I removed the "practice" table from the DBC (and the disk - it was a copy), copied the old FPW dbf to the server, added it to the DBC and made the necessary structure changes.
>>
>>I rebuilt the project and now as I try to instantiate the class, I get the C5 error. The error message points to the app object, the menuhit procedure and the createobject statement.
>>
>>All of the other classes in the vcx still operate correctly. The reports against the table I changed this morning also work fine.
>>
>>Any hope of fixing this? Or is it off to the (old) backup copy) of the vcx?
>>
>>TIA,