Re: New Era -1363 Error

Scott, FWIW, I've had problems with the -1363 error as well. Sometimes, though, mine seem to be related to timeing. For example, if I start an application and press a button "too fast" I can get a -1363. I've tried placing display statements around the button's code but it always seems to affect the timing enough to hide the error. Also, I've never been able to duplicate it in the debugger. Very frustrating! I believe that version 2.x is supposed to check for null pointers (a frequent cause of the -1363) automatically. We're on 2.0 but have yet to see any error message (either at runtime or during the compile). The -1363's do seem to be less frequent though. With nothing more to go on, we tend to blame these errors on an attempt to use an object before it is completely initialized. Usually, this just means we tell the user not to work so fast. Great fix, huh? A better way to find these errors is definitely at the top of my NewEra wish list. Also, I'd like a way to monitor string space usage (to help isolate our -1425? errors). --Craig (craig@chemistry.utah.edu) > > This is an error I posted about several weeks ago. I have not had >it occur because of a cursor returning notfound. I have had it occur >with very basic gridform supertables and with arrays that were too >large for the system. I have also had it occur because I failed to >properly declare an object. The latter was the reason given by Informix >support for most occurences. My gridform problems remain unresolved; >I merely shrunk my too-large arrays. > > I remain confused about the gridform occurances. I get them with >very small programs that have no custom coding, only pasted objects. >It has occurred with two-field tables that have only two records, and >the only pasted objects were fetch and retrieve buttons. >