Is multiple users using rbase with this connection? Dan Goldberg From: [email protected] Sent: Thursday, July 21, 2011 7:47 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: ODBC crash problem - revisited
Dan: We will be making the jump to 9.1 in the not too distant future so maybe that will solve some of our problems. In the meantime this particular problem has been giving me fits and losing me sleep. Thanks for the input. It's good to know. Mike From: "Dan Goldberg" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: 07/21/2011 10:38 AM Subject: [RBASE-L] - Re: ODBC crash problem - revisited Sent by: [email protected] ------------------------------------------------------------------------------ I use ODBC connections to various databases in Rbase 9.1 and can say it works better than in V8. Dan Goldberg From: [email protected] Sent: Thursday, July 21, 2011 6:59 AM To: RBASE-L Mailing List Subject: [RBASE-L] - ODBC crash problem - revisited Good morning: R:BASE: Turbo V-8 Build: 8.0.24.31116 OS: WinXP Pro Version 2002 SP3 I recently posted a question regarding R:BASE crashes while importing data from a SQL Server ODBC source. Long story short, I added code to my programs to create log files with the intent of pinpointing where the crashes are occurring. It appears that the crashes are occurring when the program attempts to execute the SDETACH command. Code sample: SDETACH BACOILSTATS NOCHECK Nine times out of 10 it works fine. When it does crash I can immediately restart R:BASE and re-run my program and everything is okey dokey. I will note that this problem seems to be isolated to a particular server at my location. Can anyone in our formidable knowledge reservoir suggest why this might be happening? Would it be better to SDISCONNECT before doing the SDETACH? (Obviously easy to test) I have tried coding with and without IDQUOTES. Seems to make no difference. Thanks for any suggestions or (preferably) solutions. Mike Ramsour c/o AK Steel Coshocton Works Voic: 740-829-4340 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.
