Michael,

I also wound find it strange that it could be caused by a problem in a
Menu file. But, I guess it worth taking a stab at seeing if that might
be the problem. Maybe try opening the Menu file as a DBF - Delete that
particular Menu item - Pack the Menu file - then re-open the menu using
the regular way - and Add that Item back in - and see what happens...

-K-

-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Michael Savage
Sent: Monday, February 28, 2011 12:43 PM

Sorry about the lack of detail... I've been doing some testing and this 
is confusing me...
I know that the class library must be being found for the following
reason:
In a total different menu option, I call another class from the main 
class library. It works...
I have access to the command prompt in my application, thanks to a small

program that I picked up, and inside that window, I type the line that 
creates the class I expect to see. It creates the object no complaints. 
(ie doesn't say it cannot find class main.vcx) This is inside the 
application.

Could a corruption of a menu file cause this problem. This is where I 
notice the missing classes. (There is a second class library that it 
also complains about, ocals.vcx - which holds all of my date/calendar 
controls.) Again, it too works being defined in my applications command 
window.

I'm sort of at a loss, why this problem has crept up as this was working

perfectly till late last week.
Mike

On 28/02/2011 12:09 PM, Dan Covill wrote:
>> Michael Savage wrote on 2011-02-28:
>>> To those who have replied... Thank you, but I've checked both
options:
>>> missing files due subclassing etc.
>>>
>>> One further point. It seem to happen after a particular build. After
>>> that, nothing I've been able to do will let it work.
>>>
>>> Any more ideas?
>>>
>>> Thanks,
>>> Mike
> Mike:
> Some questions and guesses:
>      Just how does it "not work"?  You said it can't find the classes
-
> how about taking the one it "can't find" and tracing it in detail,
> meaning the instantiation, the class library (or code file), the
parent
> classes, etc. etc.
>      I like the idea of removing the PJX and building it over.  Seems
> like there's some file that isn't where the PJX expects to find it.
Or
> there is a file there but it's not the right one.  The PJX looks in
the
> project local dir by default, others you have to locate.  Once
located,
> I don't think it looks in the local dir again.
>      Was there a .ERR file from the build?
>      Is there just one class it can't find, or are there several?
>
> Dan Covill

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/289ea162f5642645b5cf64d624c66a1409df2...@us-ny-mail-002.waitex.net
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to