Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,461 of 9,834    |
|    Jim Hargan to Jim Moseley    |
|    Re: Unlocking problem...    |
|    13 Apr 07 14:01:20    |
      From: noJimspam@omitThisHarganonline.com              On 13 Apr 2007 12:36:06 -0400, Jim Moseley wrote:              > Jim,       >       >> tc1 tCursor       >> PeopleKS form       >> Viewed uiObject       >>endVar       >>       >>So Viewed is a uiObject variable as far as OPAL knows!       >>       >       > It's both a uiObject variable, and a field name. It all depends on your       > scope.       >       > If you use the var/endvar listed above, then in this method 'Viewed' is an       > unassigned uiObject until you do something to it. Outside of this method,       > 'Viewed' would refer to the field name.       >       > I think there have been a few comments on naming conventions. For a defined       > uiObject, try to put 'ui' in its name, as in uiViewed.       >       > HTH,       > Jim Moseley              That was my original point. If you looked at my earlier response, I       suggested removing the ambiguity by renaming the uiObject variable to       uiViewed. I did not realize that he had been trying to attach the uiObject       variable Viewed to the uiObject Viewed, but it scarcely matters. The error       was thrown because of an unassigned variable, not by naming a uiObject that       was out of view.              Jh              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca