>Here is my code for the calling(not where Class is coded and defined):
>
>Set ClassLib To "\\gvsvr03\applications\foxapps\application_users2.0\commonappclasses" In "\\gvsvr03\applications\foxapps\application_users2.0\appusersv3.0.exe" Additive
>
>pdm_var.dc1 = NewObject("global_vars","\\gvsvr03\applications\foxapps\application_users2.0\commonappclasses", "\\gvsvr03\applications\foxapps\application_users2.0\appusersv3.0.exe")
>
>Yet it still gets put into my list of Classes when I do a build.

1. First, the SET CLASSLIB TO statement is not necessary. Remove it. Having the reference to the EXE in the NewObject statement is enough. SET CLASSLIB TO statement tends to create an early binding scenario, where the NewObject method a late binding scenario.

2. Restructure the NewObject statement to

pdm_var.dc1 = NewObject("global_vars","commonappclasses", "\\gvsvr03\applications\foxapps\application_users2.0\appusersv3.0.exe")

I found that when the path to the VCX is not required in the either statement, and that when the SET CLASSLIB TO statement is included, then the class library is placed in the project file.

hope this helps.