I once worked at a place that was soooo poor they could not afford the
patch that fixed MANMAN Version 6.1 past a certain date.  It was on a
HP3000 MICRO XE.  So we just decided to set the clock back 10 years
and hand correct (with white out and ink) any dates that had to be
printed (and sent to anyone outside the company.)

[System worked until the disc drives gave out.  It originally had 4 Eagle
drives and they started failing one by one.  I had left this company long
after although I came back (for free) to do the RELOAD every time
one of the drives HAD to be discarded.  It was eventually pared down
to two drives.  On its last legs the second drive was rented.]

Back to my point however, for your Image databases (assuming of course,
you USE Image databases,) you should do two things if your users
are going to continue to use the application:

1)  Set the database to READ ONLY in DBUTIL so that users will not attempt
to add new data.  Why?  Because they WILL.*  However, this may not be an
option in some applications, because sometimes even a "display only" function in
your application was programmed to open in READ/WRITE mode thus crashing your
app if the database is set to READ ONLY.

and/or

2)  Fill the data sets in the database to 100% full (use your favorite DB
utility if you have one.)  There may always be some empty record slots
in a Detail dataset because it will get rounded up to the nearest blocking
factor, but you can make it 100% full for Master datasets.  This way, the
application will still work with the database set for READ/WRITE, but it will
fail when a user makes the attempt to add a record.  You may still have a problem
if the users try to modify records.  Hopefully, the users won't be smart
enough to use the application's delete functions THEN try to add new records...

lastly

If the application has it's own security functionalilty you may also want to
create a "READ ONLY" type user that can only do Read Only type commands.
Then delete all other users in the application.

* (There was this user who continued to add new vendors a discontinued
application, because the user preferred the Vendor lookup capabilities of the old app.
Despite the fact that no activity was to be posted in it.  The database was only
supposed to be around for history purposes.  Filling the DB to 100% full stopped
this activity.)

-----Original Message-----
From:   Jim Norbut [SMTP:[log in to unmask]]

Hello,

I have a model 950 (dinosaur) with MPE 3.0 on it.
I know that it is not Y2K compliant (so don't even go there).

My boss and I figure that since this system is being replaced by a NT Server in August or September
and we will only need the historical refrence/lookups we can just change the date by rebooting the
system.

So on 11/30/99 we will do a reboot to make it 11/1/99 and again and again and again until the data
is not needed anymore in February/March of 2000 when we plan on getting rid of the machine.

Anyone else in the same boat as me.....will this work.

Once we get the NT server up and running we will not be adding any info to the 950's databases.
so we will not be in a situation where will we be adding new deals/info and cause date confustion.

Please send any replies to the following address:

[log in to unmask]