Hi,

I just run the Database consistency utility and we have a number of
problems with our database:

Fixed Record Length Mismatch.
Dictionary indicates length 114, Data file indicates length 126.

The table location is a full path of a relative path.

Data File Index is Not Defined in the Dictionary

To name a few. We have been adding tables and modifying data fields
for a couple of months now. The program that uses this Database (DBA
Manufacturing) is reporting wrong numbers and our MS Access databases
(ODBC) are not displaying the full table sometime, and sometime no
table at all.

I have been put in charge of the DB and I am new with Pervasive.

How can I fix this problem? How do I recreate the dictionary?

I hope you guys can help me.

We are using: Windows 2000 Server and Pervasive.SQL 2000i

Regards,
Bre-x

I have to ask exactly how you have been "modifying data fields".

If you are making changes through SQL and the application is not
(which is likely), then the application will still be expecting the
old record layout and produce incorrect results (best case).
The CheckDB report should be as consistent as it was when you started
(older application pre-date the SQL standard and usually did not
provide a correct schema if they supplied one at all).

If you are making the changes to the tables through the Btrieve API
then the SQL schema is likely to get off.

At this point is sounds like #1 and the application is starting to
fail. Go back to the original files (or at least record layout) to
make the application 100% functional again, then make changes to the
SQL schema to fix it up.
Best case is the application vendor to provide the actual record
layout expected by the application but this is rarely done
(confidentiality is usually cited).

You can rename the SQL schema (*.ddf files) and start over.
There are then a couple of options on recreating them although it is
usually not an easy task as the data files themselves contain no
metadata (except for those portions of the record that may fall on a
key). The transactional API is a typeless byte repository with the
application typically compiled with the expected record layout.

Leonard

From some regular posters on a thread a while back...
----------
Our white paper on the topic can be found at
www.goldstarsoftware.com/press.asp
-- look for the paper on accessing Btrieve files from ODBC. This
discusses the
issues at hand when trying to export Btrieve data, and also provides
some ways to
do an initial export.

If you have data structure documentation (or even better, app source
code), we
can easily build DDF's for you, and optionally handle the data export
as well.
Without documentation, the process is MANY TIMES more difficult, and
it can get
quite costly, depending on the data structures themselves.

Try it yourself (with the aid of the white paper, of course) first,
and if you'd
like help with this, let us know...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
------
From: nelsonsoft (AT) hotmail (DOT) com (Gil)
Another option BtSearch at www.nssdd.com. It can help you analyze the
structure of your files and builds the DDF files. Then it will export
to dbase or ascii formats.
Gil


On 3 Mar 2004 09:26:54 -0800, cholotron (AT) hotmail (DOT) com (Bre-x) wrote: