>I took a look at the properties and it had the wrong class library. I had forgotten about VFP hardcoding the paths. So even though I did a SET CLASSLIB to the right place in the form, it used the hardcoded paths instead. So, basically, all the changes I made to the class were never seen because it was looking at the wrong class. Who's bright idea was it to hardcode the paths, anyway?

It normally stores the relative path, not the fully qualified path.

It doesn't store the fully qualified path unless the parent class library exists on another directory, or if you move the class library to another directory that doesn't have the same directory structure.

In the properties window, the full path is resolved from the relative path for display purposes.

>
>Is there any way to fix the pathing besides hacking the VCX/SCX?
>

(if the pathing is indeed wrong in the vcx...)
Nope.
But that's pretty easy to do. The field is Classloc. It should store the relative path and full filename to the parent class library. e.g.

..\base\myparlib.vcx

I'd start by looping through all the VCXs in the project and looking for ":\" in the Classloc field. That will give you all the ones that have a fully qualified path.

Remember: Backup before making hacked changes! Just in case

>Thanks everyoe for your help. Sorry for being such a dumbass. LOL!

No problem. Remember, a dumbass wrote "Three Musketeers"! <g>