Re: Btrieve upgrade options

On May 9, 4:26 pm, "Bill Bach" <golds...@xxxxxxxxxxxxx> 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...@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support 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.


.

Relevant Pages

  • Replication left the database in a weird state
    ... On my main DB Server I'm ... publishing the database, mybigdb (540Gb data file - my drive is ... the Log transactions to be marked as ... 2- There are no additional drives on the system, so all I have is the ...
    (microsoft.public.sqlserver.replication)
  • Re: Disaster recovery - Big Time!!
    ... > Original drives that were recovered were SCSI, ... > Copy the ExMoved mailboxes to the new server ... I'd then install Exchange 5.5 on a member server that has the same ... need to run ESEUTIL /P <path to database>. ...
    (microsoft.public.exchange2000.general)
  • Re: Deleting All Forms
    ... The point that Martin was making is that since the FE is just a file on the users local PC, to update the FE its just a matter of the user copying the new version of the FE from a central location and saving it on top of the version that they have already. ... Also the statement 'I know I could just tell them to download the front end from the server but I wanted to avoid that and let them refresh in their own time' doesn't make any sense. ... I cannot access their local drives. ... At present I have the database split and the front end on ...
    (microsoft.public.access.modulesdaovba)
  • Re: Newbie to Access Developer Extension
    ... drives goes back to my university days when they where hauling out the ... I've built a two-form database that feeds tables ... in fact a full blown version of ms-access. ... docs on the server. ...
    (microsoft.public.access.devtoolkits)
  • Create SharePoint Portal failed.
    ... One mentioned ensuring that SQL Server uses a case ... 13:55:40 Service database server is 'USDC-JOHRIV'. ... Update dbo.propertylist set DisplayName = N'Last name' ...
    (microsoft.public.sharepoint.portalserver)