Mike, Just an off-the-wall thought: you haven't got a HIDE command somewhere in your code, have you?
I know that it really caught me out when I tried it! W98 (in my case) seems to have no visible idea that R:Base is running if you close whatever screen is visible without opening another one. Regards, Alastair. ----- Original Message ----- From: "Ramsour Mike" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 02, 2002 7:44 PM Subject: RE: Windows 2000 error > One thing I haven't checked yet was whether R:Base may have actually still > been running. I'm under the assumption that the program terminated entirely > but if this happens again I will check the Task Manager to verify whether or > not R:Base is still running. > > Thanks -- Mike > > -----Original Message----- > From: Bernie Corrigan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 02, 2002 1:30 PM > To: [EMAIL PROTECTED] > Subject: RE: Windows 2000 error > > > > > > > RBW 1.851 under W2K Pro: Yesterday after minimizing RBW I had it disappear > from the task bar. I thought I had inadvertantly closed the RBW window so I > opened another session. About half an hour later the first session > reappeared on the task bar. I have no idea what caused this to happen. > > > At 09:59 AM 4/2/2002 -0500, you wrote: > >While we're on the subject of Windows 2000/R:Base issues, there is one > other > >situation I don't have an explanation for. On at least two occasions > >recently (including this morning) R:Base will be setting idle and it just > >disappears -- no warnings or anything just an unceremonious shutdown. It > >just goes bye-bye. Poof! Weird huh? This happened before and I thought I > >may have inadvertently shut it down but I now find that is not the case. > >R:Base starts back up just fine with no database corruption, thank > goodness. > > > >Anyone else ever had this happen? The only programs running at the time > >besides R:Base were Outlook 98, an inactive MSN, and Norton Antivirus > >Corporate Edition. > > > >Any thoughts or insights? > > > >Thanks > > > >Mike Ramsour > > > >p.s. Looking forward to seeing a lot of you at the Conference. My boss > >came up with the money to let me go, which is pretty amazing considering > how > >tight things are where I work. Yippee!! See you real soon. > > > >-----Original Message----- > >From: Sami Aaron [mailto:[EMAIL PROTECTED]] > >Sent: Tuesday, April 02, 2002 9:25 AM > >To: [EMAIL PROTECTED] > >Subject: Re: Windows 2000 error > > > > > > > > > > > > > >Alastair - > > > >I would imagine that things are pretty hoppin' at RBTI at the moment - I'll > >put a bug in Razzak's ear to do us a full-fledged explanation on BLOBs and > >forms & report storage after the conference! > > > >Sami > > > >----- Original Message ----- > >From: "Alastair Burr" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Monday, April 01, 2002 4:33 PM > >Subject: Re: Windows 2000 error > > > > > >> Thanks, Sami, > >> > >> Anybody at RBTI like to jump in - I'm sure that this is an area where we > >> could all learn something!! > >> > >> Thanks in advance, > >> Regards, Alastair. > >> > >> > >> ----- Original Message ----- > >> From: "Sami Aaron" <[EMAIL PROTECTED]> > >> To: <[EMAIL PROTECTED]> > >> Sent: Monday, April 01, 2002 8:59 PM > >> Subject: Re: Windows 2000 error > >> > >> > >> > Alastair - > >> > > >> > I don't know of any way to check a form or report for errors in the > >> Windows > >> > version - in fact, I don't know much at all about the BLOB data - this > >> would > >> > be a good time for someone at RBTI to jump in with a better > >explanation!!! > >> > > >> > I do know you _can_ still do some things with forms and reports that at > >> one > >> > time I thought you _couldn't_ do, like: > >> > > >> > If you want to find which forms use the EEP "Button.eep" you could: > >> > > >> > SELECT * FROM SYS_FORMS2 WHERE #4 CONTAINS 'BUTTON.EEP' > >> > > >> > but that's just a teaser for my presentation on "Understanding System > >> > Tables" at the Developers' Conference<g>... > >> > > >> > Sami > >> > > >> > ----- Original Message ----- > >> > From: "Alastair Burr" <[EMAIL PROTECTED]> > >> > To: <[EMAIL PROTECTED]> > >> > Sent: Monday, April 01, 2002 12:23 PM > >> > Subject: Re: Windows 2000 error > >> > > >> > > >> > > Sami, > >> > > > >> > > I'm sure that you are right as to the reasons for crashes being > >> corruption > >> > > and/or code error but I do think that the Windows version is much > more > >> > prone > >> > > to crashes than the older Dos ones. Presumably this is simply because > >it > >> > is > >> > > much less forgiving of mistakes than it was before - fair enough. > >> > > > >> > > One area where I find it much more difficult check for corruption and > >> > errors > >> > > in the db now in Forms and Reports as they are stored differently > than > >> > > before. In the past it was possible in Dos to look at the data for > >these > >> > > sys_tables and sometimes see if they were corrupted. Now there > appears > >> to > >> > me > >> > > to be no way to know if a form or report is apparently working > >properly > >> > but > >> > > causing some problem due to hidden corruption. > >> > > > >> > > Do you know what happens to the blob data when a db is reloaded? Does > >it > >> > get > >> > > written out in the same way as the "text" data does where an error > >often > >> > is > >> > > obvious? Is there some way to check forms and reports for integrity? > >> > > > >> > > Thanks & regards, > >> > > Alastair. > >> > > > >> > > > >> > > ----- Original Message ----- > >> > > From: "Sami Aaron" <[EMAIL PROTECTED]> > >> > > To: <[EMAIL PROTECTED]> > >> > > Sent: Monday, April 01, 2002 6:27 PM > >> > > Subject: Re: Windows 2000 error > >> > > > >> > > > >> > > > Mike - > >> > > > > >> > > > In my experience, 99% of the time a fatal error is caused by either > >a > >> > > > corrupt database or an error in my program. I would do these > >things: > >> > > > > >> > > > 1. reload the database > >> > > > 2. run R:Style on the command file > >> > > > 3. clear all variables, then trace your script file thru from the > >> very > >> > > > beginning, one command at a time, with messages and error messages > >> > turned > >> > > > on. > >> > > > > >> > > > The other 1% of the time has been a bug and/or code change in > R:BASE > >> > from > >> > > an > >> > > > earlier version to the current version. > >> > > > > >> > > > If you still have problems, post your command file here. > >> > > > ----------------------------------------------------------- > >> > > > Sami Aaron > >> > > > Software Management Specialists > >> > > > 19312 W 63rd Terr > >> > > > Shawnee KS 66218 > >> > > > 913-915-1971 > >> > > > http://www.softwaremgmt.com > >> > > > > >> > > > > >> > > > ----- Original Message ----- > >> > > > From: "Ramsour Mike" <[EMAIL PROTECTED]> > >> > > > To: <[EMAIL PROTECTED]> > >> > > > Sent: Monday, April 01, 2002 8:52 AM > >> > > > Subject: Windows 2000 error > >> > > > > >> > > > > >> > > > > I am getting frequent crashes in R:Base (latest version) running > >> under > >> > > > > Windows 2000. The error I get is: > >> > > > > > >> > > > > The instruction at 0x00745x07 referenced memory at 0x1263410c. > >The > >> > > memory > >> > > > > could not be "read". > >> > > > > > >> > > > > I have done some research on this and find references to similar > >> error > >> > > > > messages related to buffer problems with Win2K that were > >supposedly > >> > > > resolved > >> > > > > with the latest service packs. I am running Win2k with service > >pack > >> 2 > >> > > on > >> > > > a > >> > > > > HP Kayak with dual 550 mHz processors and 256 mb of RAM. > >> > > > > > >> > > > > There are: > >> > > > > BUFFERS = 60 > >> > > > > FILES =60 > >> > > > > > >> > > > > environment variables set and I run with some of the Microrim > >memory > >> > > > > variables set that were suggested on the list some time ago. I > >> cannot > >> > > > > pinpoint this problem to any particular event other than it > >usually > >> > > occurs > >> > > > > while running an R:Base script that I have written. > >> > > > > > >> > > > > Does anyone have any suggestions as to what I should look for or > >how > >> I > >> > > can > >> > > > > resolve this problem? Is this a Windows 2000 issue, an R:Base > >issue > >> > or > >> > > a > >> > > > > user/programmer issue? Any help is immensely appreciated. > >> > > > > > >> > > > > Thanks > >> > > > > > >> > > > > Mike Ramsour > >> > > > > AK Steel > >> > > > > > >> > > > > Voice: 740-829-4340 > >> > > > > > >> > > > > > >> > > > > ================================================ > >> > > > > TO SEE MESSAGE POSTING GUIDELINES: > >> > > > > Send a plain text email to [EMAIL PROTECTED] > >> > > > > In the message body, put just two words: INTRO rbase-l > >> > > > > ================================================ > >> > > > > TO UNSUBSCRIBE: send a plain text email to > [EMAIL PROTECTED] > >> > > > > In the message body, put just two words: UNSUBSCRIBE rbase-l > >> > > > > ================================================ > >> > > > > TO SEARCH ARCHIVES: > >> > > > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >> > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > > >> > > > ================================================ > >> > > > TO SEE MESSAGE POSTING GUIDELINES: > >> > > > Send a plain text email to [EMAIL PROTECTED] > >> > > > In the message body, put just two words: INTRO rbase-l > >> > > > ================================================ > >> > > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >> > > > In the message body, put just two words: UNSUBSCRIBE rbase-l > >> > > > ================================================ > >> > > > TO SEARCH ARCHIVES: > >> > > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >> > > > >> > > ================================================ > >> > > TO SEE MESSAGE POSTING GUIDELINES: > >> > > Send a plain text email to [EMAIL PROTECTED] > >> > > In the message body, put just two words: INTRO rbase-l > >> > > ================================================ > >> > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >> > > In the message body, put just two words: UNSUBSCRIBE rbase-l > >> > > ================================================ > >> > > TO SEARCH ARCHIVES: > >> > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >> > > > >> > > > >> > > >> > > >> > ================================================ > >> > TO SEE MESSAGE POSTING GUIDELINES: > >> > Send a plain text email to [EMAIL PROTECTED] > >> > In the message body, put just two words: INTRO rbase-l > >> > ================================================ > >> > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >> > In the message body, put just two words: UNSUBSCRIBE rbase-l > >> > ================================================ > >> > TO SEARCH ARCHIVES: > >> > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >> > >> ================================================ > >> TO SEE MESSAGE POSTING GUIDELINES: > >> Send a plain text email to [EMAIL PROTECTED] > >> In the message body, put just two words: INTRO rbase-l > >> ================================================ > >> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >> In the message body, put just two words: UNSUBSCRIBE rbase-l > >> ================================================ > >> TO SEARCH ARCHIVES: > >> http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >> > >> > > > > > >================================================ > >TO SEE MESSAGE POSTING GUIDELINES: > >Send a plain text email to [EMAIL PROTECTED] > >In the message body, put just two words: INTRO rbase-l > >================================================ > >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >In the message body, put just two words: UNSUBSCRIBE rbase-l > >================================================ > >TO SEARCH ARCHIVES: > >http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > >================================================ > >TO SEE MESSAGE POSTING GUIDELINES: > >Send a plain text email to [EMAIL PROTECTED] > >In the message body, put just two words: INTRO rbase-l > >================================================ > >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >In the message body, put just two words: UNSUBSCRIBE rbase-l > >================================================ > >TO SEARCH ARCHIVES: > >http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
