G'day Charlie,

I feel for you!   Let's see what we can do to help.

John has already given you some good places to start.

Do you have a menu option to allow the users to set full
messaging on so they can see if there is an error message
prior to the crash?

Is it on all machines?
(I have W2K on my PIII laptop and use and develop on it.
It is rock solid.
I have one developer using it on an AMD 1.2 gig machine
with 512 meg RAM and a few times a day the server reboots.
It was known to do this prior to the developer using it
for R:BASE work so I am suspecting hardware although it is
difficult to put a finger on why.)

Try implementing this:

SOFTWARE INSTALLATION, MACHINE MAINTENANCE AND INCIDENT 
LOG                     IncidLog.doc
Designed and distributed by Tom Grimshaw of Just For You Software 
23-May-2000                   Last revised 28-Feb-2001

This sheet is to record the installation of new software or updates to 
programs, the removal of no-longer required software or mass deletion of 
files, program crashes and operating system crashes, hardware failures, 
faults, replacement and maintenance in the date and time sequence in which 
they occur.   It will then enable support personnel to more speedily debug 
any problem by correctly identifying the most recent change most likely to 
have caused the problem.   Please keep it in a handy location where it can 
easily and quickly be updated.   Hint: try a plastic sleeved folder taped 
to the side of your computer or monitor.

Machine Name/Location ___________________________  User Name 
________________________________________

Date    Time    User    Item Logged
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |
         |       |       |



At 04:21 PM 18/01/2002 -0600, you wrote:
>Is there a patch that needs to be installed for Rbase 6.5++ to work on
>Windows 2000?  Many of the users at the office keep getting windows error 
>whenever they try anything inside of Rbase.  Sometimes data is even lost 
>at the expense of these errors.
>
>Charlie
>================================================
>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

Warmest regards,


Tom Grimshaw
coy:    Just For You Software
tel:    612 9552 3311
fax:    612 9566 2164
mobile: 0414 675 903

post:   PO Box 470  Glebe  NSW  2037  Australia
street: 3/66 Wentworth Park Rd  Glebe  NSW  2037

email:  [EMAIL PROTECTED]
web: www.just4usoftware.com.au

This email and any files transmitted with it are confidential to the 
intended recipient and may be privileged. If you have received this email 
inadvertently or you are not the intended recipient, you may not 
disseminate, distribute, copy or in any way rely on it. Further, you should 
notify the sender immediately and delete the email from your computer. 
Whilst we have taken precautions to alert us to the presence of computer 
viruses, we cannot guarantee that this email and any files transmitted with 
it are free from such viruses.

================================================
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

Reply via email to