Mike,
Thanks for letting us know the status of your organization.
For your information, YES, RBTI has a special program to
assist and support any non-profit organizations and educational
institutions.
Please contact our dedicated sales team at 724.733.0053 or
via e-mail, mailto:[EMAIL PROTECTED]
If we can be of any further assistance, please feel free
to contact me.
Wishing you a Happy & safe Christmas and New Year Season too.
Very Best Regards,
Razzak.
At 08:03 AM 12/17/2001 +1000, you wrote:
>>>>
RE: Terminal Server 2000 and RBase 6.0
Hi Razzak
It would be FANTASTIC to be able to stay current, however, when you are a non-profit organisation/charitable that has a budget of only $AUS180,000 per year for all capital acqusitions sacrifices have to be made. As our Rbase software, apart from this printing issue, is working well then we have had to defer the upgrade option for the meantime.
It is our intention though to upgrade to the latest & greatest within the next 12 months, budget and resources permitting.
Wishing you a Happy & safe Christmas and New year season.
Regards
Mike Lester
Manager
Information Systems
WESLEY MISSION BRISBANE
-----Original Message-----
From: A. Razzak Memon [<mailto:[EMAIL PROTECTED]>mailto:[EMAIL PROTECTED]]
Sent: Saturday, 15 December 2001 2:21 AM
To: [EMAIL PROTECTED]
Subject: RE: Terminal Server 2000 and RBase 6.0
At 08:11 AM 12/14/01 -0800, Dan Goldberg wrote:
>I have tested it here over the network. I ran a couple of large
>reports and had no problems. I am using 6.5++ for windows.
Dan,
You have the advantage of staying CURRENT and using the latest,
greatest and The Glorious R:BASE 2000 (ver 6.5++) for Windows!
Enjoy and make sure to have fun!
Very Best Regards,
Razzak.
>-----Original Message-----
>From: [EMAIL PROTECTED] [<mailto:[EMAIL PROTECTED]>mailto:[EMAIL PROTECTED]]On
>Behalf Of Eric M. Bienstock, Ph.D.
>Sent: Friday, December 14, 2001 7:27 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Terminal Server 2000 and RBase 6.0
>
>
>Terminal Server 2000 and RBase 6.0>>.....RBase for windows 6.0
>databases.......
>>>.....it either won't print at all and will dump the user out
>>>to the TS desktop, or it will print but will still dump the user out.
>---------------------------------------------------------------------------
>
>Lucas,
>
>I suggest you do the following:
> 1. install the most recent print drivers (from the manufacturer)
> 2. upgrade to most recent version (6.5++) of R:BASE for Windows.
>I had a similar experience plaguing a client and that was the solution.
>
>---------------------------------------------------------------------------
>Eric M. Bienstock, Ph.D.
> Database Development, etc.
> Authorized R:BASE Developer
> Eric M. Bienstock & Associates, Inc.
> day: 212-978-7948 eve: 973-763-8650(8)
> FAX: 209-882-9250 [EMAIL PROTECTED]
> <http://members.home.net/ericmb/Ericmb.htm>http://members.home.net/ericmb/Ericmb.htm
>---------------------------------------------------------------------------
>
>----- Original Message -----
>From: Edwards Lucas
>To: [EMAIL PROTECTED]
>Sent: Thursday, December 13, 2001 5:59 PM
>Subject: Terminal Server 2000 and RBase 6.0
>
>
>Hi all,
>About a year ago we took two reasonably fast, very stable RBase for windows
>6.0 databases running at separate sites on NT4 servers across two remote
>LANs, and centralised them, locating them on a Windows2000 Terminal Server
>and serving them up across our WAN.
>This has resulted in two very slow, very unstable databases, loss of hair,
>sanity etc...
>The slowness is a result of lack of bandwith across the WAN (128k ISDN) and
>until we go broadband this will be the case.
>The instablility is a different story.
>This mainly relates to print jobs, although we are still getting users
>dumped out of the database for no apparent reason.
>In most cases when the print job fails:
>OUTPUT Print.rep
>WRITE 'PRINT Bla WHERE bla = .bladebla'
>OUTPUT SCREEN
>RUN Print.rep
>ERASE Print.rep
>it either won't print at all and will dump the user out to the TS desktop,
>or it will print but will still dump the user out.
>Mostly the size of the print jobs are only a few kb, but to print to an
>700/800/900 series HP deskjet can take an eternity. The HP lasers 5P/6P/2100
>etc. seem quicker and more reliable but still suffer from the same problems.
>At present we have about 70 network printers running off the server (dual P3
>733 2Gb ram) and are averaging about 10 RBGTIME sessions and 3 MSACCESS
>sessions. The users are running a mixture of win95/2000 desktops.
>We've tried several things including:
>Making sure the names of the printers are the same at both ends.
>The local printer ports are set to ECP (HP recommends this).
>The paper size settings are consistent across client and server.
>The latest drivers are loaded (windows95 drivers loaded on the server where
>needed).
>Tidying up the code:
>Being meticulous about declaring/clearing variables.
>Breaking down the code into smaller procedures.
>Have been scouring this list for similar problems but it seems that
>TerminalServer2000 is not a common platform amongst you guys (probably for
>good reason).
>Any help would be very much appreciated.
>Regards
>Lucas Edwards
>Wesley Mission Brisbane
===================================-============================
R:BASE Developers's Conference: http://www.rbase.com/conference
Official R:BASE List Server: mailto:[EMAIL PROTECTED]
RBTI Events/Training: http://www.rbase2000.com/events
R:DCC Members: http://www.rbase2000.com/rdcc
================================================================
R:BASE, Oterro & R:Tango are registered trademarks of RBTI.
==================================-=============================
================================================ 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
