>Could it be a pathing issue?
No but I might add it's only the compiled .exe that's affected, even though I've not changed it for weeks. In my development, it always works. strange eh?
>
>Glenn
>
>>I had mentioned several weeks ago about animation.vcx that I have included in my .exe that works fine 98% of the time. For example, I had not touched or revised this application for at least a week and today for no reason the "blah blah is not an object" message appears and the app bombs out. It worked flawlessly yesterday and beyond will most likely work tomorrow. But not today. COuld this have something to do with MS updates?
"Build a man a fire, and he's warm for a day.
Set a man on fire, and he's warm for the rest of his life."