Very Computer

Hope some resident PDOX gurus can fill in the blanks here...

Scenario:
We are currently in the process of porting our networked Paradox
3.5/WP51 proprietary database into a beefier Java/NT environment. In
the interim (which should take at minimum 7 months for us to farm out
the project). The originator of the current system is long gone and
far away... We will be switching from OS2Warp servers w/Win95 clients
to NT Srvrs with NT wrkstns and Win95 clients. (I'm the NT guy in this
dept.)

The current configuration works...but the help desk is fielding
multiple calls daily from our various offices with complaints of
corrupted index files and other db related tragedies. They are
spending a great deal of time diagnosing and restructuring files. We
are hoping to minimize these occurrences, assist the helpdesk dept.,
and stop the complaints by introducing a more stable environment

I have been scoping this NG and have seen many references to the fact
that PDOX version 3.5 is incompatible w/ Win machines and it appears
that v. 4.02 could solve some of the problems extant.  My questions
are the following:

Is 4.02 the best version as far as compatibility with v.3.5?
Where can I obtain this version?
Is 4.5 (which we have) compatible as well?

What exactly is entailed in the process of installing/net setup of
version 4.02....Are db, scripts, lib val and WP51 macros all
compatible?

I assume we have to recompile the scripts, are there any other known
particulars, in regards to implementation issues or snafus that may be
involved with an (pseudo)upgrade of this nature?  

Many thanks in advance for any pertinent info!

PT:

I'm sure that others will also chime in with more information or
confirmation of this.

Pdox4.02 or Pdox4.5 is designed to be run under winduhs so you should
jump there.  Pdox4.02 will allow the least cosmetic changes to your
pdox3.5 app - scripts, libraries will have to be rebuilt, recompiled,
converted.  If you have Pdox4.5, any number of supporters on the NG
can "downgrade" to 4.02 for you.

The situation (index out-of-date) that you're discribing sure sounds
like an opportunistic locking problems, where you would turn off all
of that cr*p from both the server and workStation level.  You might
search for threads in that direction for the instructions (also over
on corel.cnews.ca) but wait for confirmation of this information prior
to doing it (the information on other threads is regarding PdoxWin -
that's why I'm hesitating).

HTH.

Bob

restructing doesn't fix damaged tables.. you must rebuild with tutility to
do that..

Quote:> Is 4.02 the best version as far as compatibility with v.3.5?

yes.. that's what you need to get.. you shouldn't be using 3.5 under
windows..

Quote:> Where can I obtain this version?

buy any version of 4.0 or later, dos or win, and you can legally
"downgrade" to 4.02.. e-mail me for details..

Quote:> Is 4.5 (which we have) compatible as well?

4.02 is better for running 3.5 apps.. but there's your ticket for it!

Quote:> What exactly is entailed in the process of installing/net setup of
> version 4.02....Are db, scripts, lib val and WP51 macros all
> compatible?

yes.. you need to rebuild and restruct all tables to Standard format
tables and re-compile your lib..

--
Steve Green
Corel CTech - Paradox
Diamond Software Group, Inc.
Waldorf, Maryland  USA

http://www.diamondsg.com

Can't answer the WP51 Macro question.

I replaced many of a clients WP51 Macro calls with some
plain old PDOXDOS reports (with some not so Plain printer tricks using
a HP PCL5 level printer).

These were form Letters with a simple WP Text base Logo Letterhead.
Needless to say, the simplicty maxed out and the speed went from
Hours(for the WP macros to grind) to as fast as the LJ5si could spit
out pages.

Except for some Wait Table Prompt Differences ( 4.x only has one line)
most scripts convert well.
SomeMenu navigation by keystroke may need to be adjusted if used
(Right Right Enter)
IMHO it is alway better to be explicit whe navigating the Menu.

Add SetUiMode Compatible Compatible to the beginning of the startup
script.

Steve U
        _
       | \                           Steve Urbach
       |  )erek

  / / /                              http://www.greenduck.com

Thanks to all who replied and emailed!
I know I'll be posting to this forum again and I appreciate the
information.