Anthony, the problem I referred to is specifically dos.  The new simulated dos in 
XP/2000 does not reliably free memory.


"Anthony Schmidt" <[EMAIL PROTECTED]> wrote:

>Albert:
>
>RTW 6.5++ is even more picky than RBW 6.5++
>
>One thing I found to be a problem is setting the location of the PAUSE and 
>DIALOG boxes on-screen.
>
>The documentation states that you can locate them down to row 25, but I've 
>found that placing below line 19 will cause unreliable behavior. I have 
>experienced RTW crashes when I've set the locations �to values outside the 
>range of �1 to 19. 
>
>In addition, make sure that you set BUFFERS and FILES to 60. Even though 
>RBW and RTW are Windows programs, and these environment settings are 
>supposed to affect only DOS programs, they do have an effect on RBW and 
>RTW.
>
>Why not use Visual Basic with the RB ODBC or Oterro drivers instead? I've 
>spent a good deal of time in the last few weeks working with VB 6, and 
>have found it to be a very robust environment to work in. Some things 
>require more coding than RBW, but there are a great number of things you 
>can do with VB that are just not possible with RBW and VB provides a 
>tremendous level of granularity of control. 
>
>It's fun and you can do it your way!
>
>If you are interested in learning how to use VB as a database front end, 
>take a look at Murach's Visual Basic 6 book.
>
>Good luck!
>
>Tony
>
>Anthony J. Schmidt, JD
>President
>The Computery Ltd.
>One East Main Street
>Bay Shore, NY �11706
>
>631-665-8100 Voice
>631-969-5988 FAX
>
>http://www.computeryltd.com
>
>
>
>
>
>[EMAIL PROTECTED]
>04/02/2002 11:51 AM
>Please respond to rbase-l
>
> 
> � � � �To: � � <[EMAIL PROTECTED]>
> � � � �cc: � � (bcc: Anthony Schmidt/BayShore/SGU_LN)
> � � � �Subject: � � � �RE: Windows 2000 error
>
>
>I ran 6.5 RBwin + and ++ on win2k pro without any problems. Now I am 
>running
>it on XP Pro without a hitch.
>
>When debugging I have noticed it will kick you out if their is something
>wrong with your code. It should tell you the error but it kicks you out
>instead. It can be mistaken for something that can be wrong.
>
>As Rbwin has evolved, it has become more picky on proper coding (like
>parenthesis in report variables).
>
>
>Dan
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>Behalf Of MJS
>Sent: Tuesday, April 02, 2002 8:17 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Windows 2000 error
>
>
>Albert,
>
>This would seem to be a pretty big problem. �Is it reproduceable? �I would
>like to upgrade stations to Win2K, but if this is just begging for 
>trouble,
>then that would be a bad idea. �How do you demonstrate the problem?
>
>Mike Sinclair
>
>Albert Berry wrote:
>
>> We have found in testing that W2K does not properly release memory taken
>by R:Base during processing. �Our solution is to periodically exit R:Base
>and go back in. �We did run a command file that looked up the compspec, 
>and
>did a
>> ZIP RETURN &vComSpec /c EXIT
>> periodically, but that has recently failed us. Another list member
>suggested ZIP RETURN /cmd, but I have not been able to test it yet. �The
>user is exiting RBase frequently to ensure that the memory does not get
>eaten, and has not crashed.
>>
>> Ramsour Mike <[EMAIL PROTECTED]> wrote:
>>
>> >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/
>> >
>>
>> __________________________________________________________________
>> Your favorite stores, helpful shopping tools and great gift ideas.
>Experience the convenience of buying online with Shop@Netscape!
>http://shopnow.netscape.com/
>>
>> Get your own FREE, personal Netscape Mail account today at
>http://webmail.netscape.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/
>


__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the 
convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.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/

Reply via email to