On May 9, 4:26 pm, "Bill Bach" <golds...@[EMAIL PROTECTED]
> wrote:
> 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.
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.
>
> 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
> BillB...@[EMAIL PROTECTED]
> http://www.goldstarsoftware.com
> *** Chicago: Pervasive Service & Sup****t Class - 07/2007 ***
>
> Distalgesic wrote:
> > 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.
|
