Jon,

I know I sound like a broken record here, but here goes. . .

Might there be some place where you use the Cls *method* in your code, and you have no period before it?

Do you have the string CLS (in any form, eg cLS, cLs, CLs, etc and also intended to be, but possibly mis-typed, as *part* of any word/variable/etc) anywhere in your code or in qualified TAGs or in Triggers/Referential/etc code?


Again, good luck,

Jim N

>>Jon,
>>
>>Check the events for the combobx, don't skip any of them no matter how far fetched you may think they are. Double check all of the combo's properties, in the property sheet you can right click and choose Non-default properties only to aid you in checking everything.
>>
>>Watch everything carefully, a , where a . should be can cause a problem and a . where it doesn;t belong can also cause difficulty.
>>
>>The best I can tell you is that I have never had this happen related to a table with bad records. Something is trying to muck with CLS and CLS doesn't exist.
>>
>>After you check the combo, check the class it comes from. Does it come from one of the VFP class libraries?
>
>Jim,
>The ComboBox is based on the Base Class. One thing I hadn't mentioned before was when the last record in my JOBHD file had a CustID of SWFT and I hit my ADD Button I would get an error that stated something about an "Object not found." I can't seem to reproduce this error now though.
>
>Also, this is actually the second time something like this has happened. I had a customer with the CustID of TROY (Troy Manufacturing) I worked around it in the same way. Left the record and added another and changed the CustID value in the respective header files. I have since removed that record though.
>
>I will continue to try and narrow this sneaky sucker down and keep you posted on any info or additional questions I may have.