dbTalk Databases Forums  

ODBC Error: SQLSTATE = S1000, Native error code = 0

comp.databases.btrieve comp.databases.btrieve


Discuss ODBC Error: SQLSTATE = S1000, Native error code = 0 in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Bre-x
 
Posts: n/a

Default ODBC Error: SQLSTATE = S1000, Native error code = 0 - 03-14-2005 , 10:10 AM






Hi,

everytime we want to open a table using Pervasive Control Center, we
get the following error:

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

Also we noticed that the X$file, X$Field and X$Index are empty.

one way to fix this problem was copy these files from a backup.

But today not even that is fixing the problem.

We cannot connect any crystal o ms access reports to the sql server.

Reply With Quote
  #2  
Old   
Leonard
 
Posts: n/a

Default Re: ODBC Error: SQLSTATE = S1000, Native error code = 0 - 03-15-2005 , 01:53 AM






Strange and bizare.
The system tables x$file and friends are the SQL schema for the data
files. If they are empty then there is no SQL schema.

Since you have empty ones instead of populated ones or none at all it
would almost sound as though somehow the database is getting created
on top of itself. Normally that just picks up the existing ddf files
unless the old ones are removed first. Uninstalling the database
engine does not do that. Once you get the files restored from backup
and the engine picks them up you might want to flag them read-only to
keep them from disappearing again.

Leonard

On 14 Mar 2005 08:10:49 -0800, cholotron (AT) hotmail (DOT) com (Bre-x) wrote:

Quote:
Hi,

everytime we want to open a table using Pervasive Control Center, we
get the following error:

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

Also we noticed that the X$file, X$Field and X$Index are empty.

one way to fix this problem was copy these files from a backup.

But today not even that is fixing the problem.

We cannot connect any crystal o ms access reports to the sql server.


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.