Very Frustrating (OpenInsight Specific)
At 12 APR 1999 07:09:44AM Simon Bowyer wrote:
I have just experience and very frustrating "feature" in OI. A colleague was doing some testing and had moved his PC date on a day. He then re-compiled a form with a create event. I also, some while later, compiled the same form having made some changes to the create event. My changes did not compile. It would appear to be because the other PC's date was in the future. As soon as I changed my PC date forward, my changes appeared - along with various messages, debugs etc that I had added in an effort to find out what was going on i.e. no debug, no message, no fixed code……..etc.
I thought other people might like to know about this to save them from wasting time like I had to.
At 12 APR 1999 09:40AM ArjunRevelation wrote:
I tried to reproduce this problem, using a form with no control and a form associated with a database having a few controls and picked out random dates in the future; 2001, 2005,2010, 2017. Both the forms compiled fine and there was no problem. I have tried this on the latest version of OI-3.71. Could you give some more information on what specific controls you have on the form and which OI version is being used?
For more information on OpenInsight and Y2K compliance, refer to the document listed below
At 12 APR 1999 10:19AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
I was fully able to duplicate this functionality, as expected. Haven't decided if it's a feature or a bug, but it's been there since OI 2.0, though since windows and events appear to have differing responses, I'd say there's a bug somewhere, but I'm leaning towards the compilation of the window being a bug, not the failure of the event's compilation.
I'll give you a few hints on finding the source of the problem. First off, it's not the compilation of a form that's at issue, but an event. Next, check out the various repository function arguements.
Thinking about offering up a Sprezzatura fountain pen to the first person posting the correct explanation.
At 12 APR 1999 04:01PM Eric Emu wrote:
The compilation dates prevent the CPU CS:EIP
registers decrementing rather than incrementing.
This means your application doesn't run backwards.
Otherwise there'd need to be a READPREV command,
a JUSTINCASE command, and a PRNSTAT() code asking
you to remove all the blank paper from the printer
because a paper jam is about to occur.
Eric