Good point, there's no rush but I'm sure that more information on blobs would be useful.
Perhaps it's a good subject for one of Razzak's "From the Edge" explanations when he has the time? Regards, Alastair. ----- Original Message ----- From: "Sami Aaron" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 02, 2002 3:24 PM 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/
