dbTalk Databases Forums  

Re: W98 SQL V8 Client Problems

comp.databases.btrieve comp.databases.btrieve


Discuss Re: W98 SQL V8 Client Problems in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
rwickers
 
Posts: n/a

Default Re: W98 SQL V8 Client Problems - 06-25-2003 , 08:21 AM







Matthias,

This error 14 is this a Btrieve error status? What format are the db
files you are using? A butil -stat operation of a data file will tell
you. I have not heard of such problems. I'll talk to a few colleagues
about it and get back to you.

Regards,

Randy Wickersham
Pervasive Software Inc.

--
Posted via http://dbforums.com

Reply With Quote
  #2  
Old   
Matthias Hartmann
 
Posts: n/a

Default Re: W98 SQL V8 Client Problems - 06-25-2003 , 02:01 PM






Hello Randy,

to come to the most important point first I'm unfortunately not a database
expert.
The application my customer is running is DOS-based and was specially
designed for him several years ago. Because he has bought his new server
from me an not from his software developer's company they're a little bit
angry and not very helpful. Their succinct answer: "This is not a problem of
our application".
I've investigated that the error numbers are eqiuvalent to the Btrieve error
status codes and the db files are in the version 5 format. And maybe this is
the problem. Can you tell me how I can convert the db-files in the new
format?

Regards,

Matthias



Reply With Quote
  #3  
Old   
rwickers
 
Posts: n/a

Default Re: W98 SQL V8 Client Problems - 06-25-2003 , 03:05 PM




Matthias,

You can rebuild the files with the Pervasive GUI utility called
"rebuild". First you enter a list of files. Then you start the rebuild
process. Back up your files first.

Regards,

Randy Wickersham
Pervasive Software Inc.

--
Posted via http://dbforums.com

Reply With Quote
  #4  
Old   
Matthias Hartmann
 
Posts: n/a

Default Re: W98 SQL V8 Client Problems - 07-18-2003 , 01:14 AM



To complete this thread: The Problem is solved, it was caused by long path
name. The database path was "sys:longpathname\database" with a root mapping
from "h:" to "sys:longpathname". The program refers to "h:\database". After
renaming "sys:longpathname" to "sys:shortpn" and changing the root mapping
it finally works.
The strange thing is that under NetWare 5 the path name was identical long
and the database worked fine. As mentioned the problem only occured with
Windows 98 clients and depended not upon the NetWare Requester version.

"Matthias Hartmann" <matthias.hartmann (AT) stencode (DOT) de> schrieb im Newsbeitrag
news:bd6voh$pp667$1 (AT) ID-101388 (DOT) news.dfncis.de...
Quote:
Hello,

after hours of unsuccessful search I have decided to put my problem in
this
NG.

A customer has updated his NetWare 5.0 Server with a Btrieve 6.10f
database
to NetWare 6 SP3 and Pervasive SQL V8 SP1 and has now problems to work
with
the database from his Windows 98 SE Clients. The PCs have NetWare Client
3.32 SP2 and SQL V8 Client installed and it is a pure TCP/IP environment.

From Windows 98 Clients it is possible to login into the database, to view
and to change records but if you print or create a new record it results
in
an "error 14".

With a Windows XP Client (NetWare Client 4.83 SP2 and SQL V8 Client) it is
possible to print and create records.

Any suggestions?

Thanks in advance

Matthias





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.