Hi,

I've gotten a little farther. Any help anyone can provide on the problems
below would be appreciated.

I start Pervasive.SQL Control Center. I see both computers (mine and the
remote) under 2000i engines. I'm running 2000i SP4.

I copied the database from the host computer to my local machine because the
Pervasive.SQL Control Center wouldn't connect to the remote PC's engine
(Problem 1). The error is: Connection to the engine HOSTPC failed. Make
sure that all components are installed ... It's installed and running.

Back to Control Center. Under my computer I see two databases: DemoData
and NB_LOCAL.

I expand DemoData and click on Tables. I see the various tables in the
right pane. I double click on the Student table and I see data.

I expand NB_LOCAL and click on Tables. I see all of the various tables in
the right pane. When I double click on any of them, I get this error
message (Problem 2):

ODBC Error: SQLSTATE = S1000, Native error code = 0
Unable to open table: Address.
No such table or object.

Now that's funny, I can see the table in the Control Center so it exists.
In SQL Data Manager I click on File and Open Database. Security is not
checked. I check it and type in my user id and password. No error. I
execute the same SQL again ("SELECT * FROM "Address") by hitting the execute
button. Same ODBC error. I tried the administrator's id and password that
was set up through the application that maintains the database. No
difference. There is no ODBC entry on the host PC so I didn't create one on
my computer.

I right click on Address and choose properties.
Table name = Address
Table location is empty
Dictionary Path = c:\program files\...
The rest of the properties say "no file".

The dictionary path points to the application software directory in Program
Files. Should it point to a file rather than a directory? I'm not able to
edit the field. In this directory is FILE.DDF and it contains field names
for .DBP's I'm interested in, including Address. I don't see any directory
names in this file.

I right click on Address, choose Tasks and Edit Design. The field names,
types and sizes are displayed. All fields but 1 have "Case" checkmarked.

I right click on Address, choose Tasks and Export Data. I go through the
wizard and get this error:

Error [Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine
Interface]Unable to open table: ADDRESS

Where do I go from here?
-- Scott

On Wed, 21 Apr 2004 16:36:37 GMT, buildpc (AT) hotmail (DOT) com wrote:

Workstation, Workgroup or Server engine?
The workstation engine does not accept remote connections of any kind.
The workgroup engine should for configuration but not under the remote
server databases. This architecture changes with Pervasive.SQL V8
Workgroup.
If you can not connect at all to the workgroup or server engine you
may need a published patch:
http://www.pervasive.com/support/upd...00i_hotfix.asp
see: Pervasive.SQL 2000i Workgroup & NT/2000 Server (1.5 Meg)

Although there can be other issues ranging from no name resolution
(does ping by name return the correct address) to firewall software
blocking the request to another process hijacking the well known
listening network port.
Not necesarily. The SQL schema for the table has to exist, but not
the physical file defined to be the logical table.

SQL security is NOT related to accounts on the computer.
If it is set it is internal to the database.
To see if it is set, right-click the database in the Pervasive Control
center and select "Properties" then select the "Security" tab.
If security is not turned on "logging in" has no affect.

The PCC only shows databases that are registered as ODBC DSNs.
Did you create the database through the PCC? If so check the system
dsn tab on the ODBC administrator.
This would indicate that the database engine can not find the data
file.
Pointing to a directory is correct. Double check the spelling or
browse to it, but from below it is probably correct.
The directory must be a physical local directory (except with WGE).
The lack of hard-coded directory paths in the DDFs is good. Double
check that there are no relative paths either.
1) double check the Named Database configuration. I should point to
the DDF files. From the description it does.
2) open the X$File table. If you do not see the X$File table, check
the "Show System Tables" under the View menu in the PCC.
A) make sure the table name "ADDRESS" appears in the field "xf$name".
B) double check the file name for the table in the "xf$loc" field.

If the above is correct it may be a different file that can not be
opened. The shortest way to determine which one is to run a
MicroKernel trace.
-----------------
To turn on the MicroKernel trace:
1) start the Pervasive Control Center (PCC) on the server
2) expand "Pervasive.SQL 2000i Engines"
3) expand the server name
4) expand "Configuration"
5) expand "Server"
6) select "Debugging"
7) as we are more interested in the operations performed than all the
data, set the "Number of Bytes from Data Buffer" to something smallish
- 32
8) we will still need to get file names as passed in the key buffer,
set the "Number of Bytes from Key Buffer" to 80 or more.
9) Select Operations should be "All"
10) "Trace File Location" can be anywhere that is convenient and has
space.
11) Set the "Trace Operation" to "On".
12) Select the "Edit" menu and "Apply". Note, this is the one setting
that the message is incorrect about having to restart the engine.
13) Reproduce the error (if possible), or just run the application as
normal to capture the operations it performs
14) Set the "Trace Operation" to "Off".
15) Select the "Edit" menu and "Apply". Note, this is the one setting
that the message is incorrect about having to restart the engine.
-----------------
The trace file produced is plain text so use your favorite viewer /
editor. The issue will normally be logged at the end.
Look for an Opcode : 0000 in and a non-zero Status : out.
File open errors are typically status 11, invalid filename / directory
or status 12, file not found.
The key buffer will contain the path of the file trying to be opened.

Leonard