We currently have a Novell Netware 3.20 based Btrieve 6.15 legacy
application which we are looking to hopefully migrate to a newer
platform. The legacy application is DOS-based and has some quite tight
memory restrictions.

I have downloaded some trial versions of V9 and installed it on a
virtual server but am struggling to see how to get my existing files
to be recognised by the server. I created a database and pointed it at
a folder containing my files but nothing seems to be happening.

I know I've done something wrong but can't seem to find anything about
doing this sort of upgrade.

Plus, will I be able to use my 6.15 requester to access the files on
the new server setup as I don't really want to have to fiddle about
with my client setups.

PSQLv9 does support the use of the old DOS requester, but this is NOT
recommended. In fact, you'll still be fighting the same memory issues,
and you won't see many of the benefits of the newer engine.

Instead, install the PSQLv9 client on the workstations. This will
install the DOSBOX redirector, which redirects DOS application requests
through the Windows 32-bit requesters. (WinNT+ machiens are automatic,
whereas Win98 machines need to manually load BTRBOX95.EXE and
BDOSSTUB.EXE.)

As far as recognizing the files, please note that the PSQLv9 engine
requires files to be in at least Btrieve 6.x format. If you have old
Btrieve 5.x files, you may get Status 46's trying to make changes, as
PSQLv9 doesn't support writing to the older format. However,
rebuilding the files is simple and easy.

Other than that, you should not need anything else. Files are never
"seen" by the database until the application attempts to open them, and
usually this is done through a drive letter connection or UNC pathname.
As long as the app knows to open the files on (for example) Drive K,
and if drive K is mapped to the database server, then all should work.

If you get Status 11, 12, or 35, try disabling the Client-side setting
for "Embedded Spaces", as some older apps use a space as a filename
terminator.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 07/2007 ***



Distalgesic wrote:

On May 9, 4:26 pm, "Bill Bach" <golds... (AT) speakeasy (DOT) net> wrote:

So basically I copy my existing 6.15 files into a folder, tell the
management console where the database is, map up my drives and launch
my application and away we go?

I will try the existing requester first then give the new one a whirl,
don't want to be having to change too much at once, got over 100 PCs
connecting to the legacy server so a server replacement initially
would be less work.

Mostly. Remember that the old DOS requesters are hard-coded to use SPX
as a transport protocol. If you try to use them on a newer Windows
server, then you'll need to properly install and configure SPX on the
server as well. (Please see the MS docs on this -- most people
configure SPX incorrectly when they try to do it.)

The newer DOSBOX redirector goes through the Win32 client, and thus
uses TCP by default, which is much more efficient, and usually faster.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 07/2007 ***


Distalgesic wrote:

On May 10, 2:09 pm, "Bill Bach" <golds... (AT) speakeasy (DOT) net> wrote:
Many thanks for you help mate, am setting up a virtual PC to do my
testing so will go straight to the IP config and see how we go .... I
may be back for more help real soon