Hi Craig,

[ I am no longer running any of these. I no longer
work for the VAR, who still does actively have
customers running these configurations... ]

I worked for a VAR who had acquired an
mvBase 1.3.02 application from another VAR,
written in mvBASE, which they run on Windows.
Some customers are running older NT 4.0 Servers,
others running W2K Server, yet others running
W2K3 Server. The goal was to try to move the
mvBase application server as forward as possible,
which, for us, was mvBase 1.3.02, PS 8, on all
above mentioned, replacing older WinNT 4.0
Servers with latest versions of Servers, running
W2K3 Std Server. PS8 is required to handle newer,
more secure aspects of telnet connected sessions.

RD played the same game - you need to update to
latest version, and not run as a service. We had a
good number, if not most, customers running as
a service, and did not see too many, if any problems.

But, ...
To be safe, run it as an application.

End user customer shops need to be educated on proper
mvBase startup and shutdown procedures, often requiring
command line knowledge, to get the database properly
shutdown, before attempting to get the Windows platform
shutdown, Windows Updated, or otherwise rebooted.
An intelligent UPS with auto-shutdown software is a
must have requirement as well.

RD did claim that they had some "magic" in later
releases, which may help alleviate timing and time
routines, (apparently underlying chnages in Microsoft
OS levels that affected time and timing routines),
but as you said, updating to PS 9, or 2.0.X Releases,
required signing new license agreements,
which would have required exisiting customers
pay exhorbitant fees to come in license compliance.

[ Apparently RD knows the trend to run mvBase as a
backend server through a web-server, avoiding
con-currently connected users in the old "PICK Seat"
licensing scheme-ology. Too bad they can not come
to a more reasonable compromise - if they made it
more reasonable, many would consider the upgrading, a
nd it would be a better source of revenues for RD then
keeping it high/unreasonable, playing hardball, which
further discourages customers and VARS from coming
into compliance under their new licensing scheme-ology. ]

The company I worked for at the time decided to
not pork their customers over, or to attempt to
pay those licenses themselves. The idea was to
keep an active eye on the Servers and their
behavior for the time being, while development
engineers at the newer, larger VAR looked at
attempting to migrate/replicate the applications to
SQL-Server.

I hope this information is helpful.



"Craig" <xxxxjjjj (AT) erferf (DOT) com> wrote

It helps quite a bit

Thanks for the reply Scott

Craig

"Scott R." <Wonderful_SPAM (AT) spamcentral (DOT) net> wrote

Hi
An interesting problem. I wonder if someone is using the proper date format
occasionally which in D3 is SET-DATE-EUR rather than the rather peculiar
American way of confusing the month and day .
Good Luck
Peter McMurray
"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote

Goo'day, Peter,

I'll whisper it to you before anybody else shouts:,

On Sat, 12 Nov 2005 21:30:35 GMT, "Excalibur"
<excalibur21 (AT) bigpond (DOT) com> wrote:

The OP *did* mention the "time seems to be arbitary", so perhaps it
really is a greater problem than day/month vs month/day unless they -
Septics - now play havoc with the display of time too......... and,
really, that wouldn't surprise me....<g>


Bruce Nichol
Talon Computer Services
ALBURY NSW Australia

http://www.taloncs.com.au

If it ain't broke, fix it until it is....

Bruce Nichol wrote:
I remember seeing this problem on Mentor PRO 4.0/4.1, although I can't
remember if there was ever a resolution (I left the company before it
was ever properly resolved). Don't know if that would make you more
likely to think it might be mvBase, or hardware...

--
PeteJ