>Really confusing. Im not sure if its data,software, or a combination of the two.

this is a long shot but I had some similar weirdness with a data environment class that got whacked. Try editing the bizobj, clear current data environment in the builder and save it with no DE and close builder and close class designer. (If you dont save/close for some strange reason the builder likes to start putting table/view names in double brackets for this next step that get buried deep in the vcx and your weirdness gets worse)

Now go back into the bizobj and get into the builder and define a brand new data environment and see if that fixes things.

Note for Kevin - this double bracket bug around the value specified for "cursorsource" on cursor objects (shows up in properties tab of vcxedit form) has been haunting me for months... problem is everytime it hits me I either dont have the time to try and recreate it & I cant put my finger on exactly what causes it in order to pass it onto you. Or if I do have the time to tackle it the darn bug hides from me and I cant recreate it the second time. But as soon as I'm under deadline and, it comes right back to bite me again.

I've seen it in multiple projects now, and many different bizobj/dataenvironment combinations. As far as I've been able tell, it only hits when removing a reference to an exisiting data environment (already saved to adataenv.vcx) and specifying a new or different data environment class. It also seems most prevalent with DE classes that have a free table in it as secondary lookup... but not always, I have gotten it once on a straight local view DE with only one updateable view as my lone cursor object. If you havent seen this yet let me know & I'll give it another try at forcing it to happen and see if I cant get it documented more specifically instead of just kicking the wall and griping about "no wonder Kevin gave us vcxedit" ;)