And of course, I am starting to get errors. Here is a super stupid question --- How do I decifer the error #'s??? For instance, I get Error #1733 often -- what does it mean?
Greetings Lynette,
Class definition "name" is not found (Error 1733)
The class definition specified in a CREATEOBJECT( ) function cannot be located.
Open help, go to the Search tab. Type "err" and one of the listings will say error codes by number, by alpha... etc.
Consider that ADDOBJ() may have failed and then you tried to reference that item.
If you are using object menu classes there are number of known bugs that must be corrected (once). Search the forum. I know that the "admin" menu pad needs to be renamed to "aadmin" because... the standard behavior of the menu is to remove the first character ( c, i, or a) and replace it with a "o". So your class may be called aSearchFormBar, but during run time it is in fact oSearchFormBar. For some reason a few menu pads and bars come out of the box without a prefix character.
As clock status... sounds like something on the preference form. I can't say because I turned off the prefenece form.
What you have to remember is CB is a learning exercise. The preference form provided is just an example of how you "could" implement a preference form if you need one. It is a common need... but if you don't need it...
and chances are, if you really need one it isn't to set the clock on or off. There would be some other complex prefences your application requires, so you'll have to create your own custom preference form.
Turn on the error checking. It will log errors (but not help with the numbers) and memory status. In iApp.vcx open your LoadChildren() method and include:
** oError
lnChildNu= ( lnChildNu +1)
laChildren[lnChildNu, CHILD_CLASS] = This.cErrorManagerClass
laChildren[lnChildNu, CHILD_NAME] = This.cErrorManagerobject
then set the property
.cErrorManagerClass= iErrorMgr
.cErrorManagerObject= oError
Then you will be cooking with gas. Hopefully I haven't just opened up another thing to debug... but it will pay for itself. You want this error trapping when start developing.
If you don't see the "debug" button on the error manager form, open the class and look for a property that will identify you as a developer. Then you will be able go directly from the error form into the debug window and see the step that created the error.
HTH
James Sayer
©2001 James Sayer |
