John: Not recently but that's a good reminder. I think when I checked them before there wasn't a lot of useful information as to the exact nature of the crash.
It bears checking again. Thanks for the suggestion. -- Mike From: "John Engwer" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: 06/22/2011 02:35 PM Subject: [RBASE-L] - RE: Microrim variables and FILES setting Sent by: [email protected] Mike, Have you looked at the event log to see what OS errors are being posted at the time of the crash? John Engwer (412) 751-2433 From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, June 22, 2011 1:56 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Microrim variables and FILES setting Good afternoon: I'd like to hear comments from anyone who might be using the MICRORIM_F2MAXBLK and MICRORIM_F3MAXBLK variables and the FILES setting. I'm using Turbo V-8 on Windows XP Pro w/SP3 on a machine with 4GB of RAM. My reason for asking is that I am experiencing sporadic crashes of the RBG8.EXE program while extracting data from a SQL Server database via an ODBC connection. The best I can determine is that the crashes are occurring at the moment that I am inserting the last record of the selection into a local R:BASE table. The crashes are of the sort where I get the nice little box apologizing for the crash and do you want to send the information to Microsoft. Until I clear this box the database is locked and I restart R:BASE. A DBA consultant suggested that I bump up the files and buffers on my system. The crashes are sporadic and impossible to trap for as far as I know since it kills R:BASE. Thanks for any suggestions. Mike Ramsour c/o AK Steel Coshocton Works Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed and may contain privileged, proprietary, or otherwise private information. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed and may contain privileged, proprietary, or otherwise private information. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.
