Download User`s Guide

Error Messages from PCC
„
„
The operating system may be expecting the user to change his/
her password on the first logon. The Create Database Wizard
does not allow this, so the connection fails. On Windows NT,
this situation occurs if, in the User Manager, you have selected
the User Must Change Password at Next Logon checkbox.
If the user is a member of another group with lesser permissions,
the lesser permissions will override the greater permissions. A
user always has the most restrictive permissions of any group to
which the user belongs.
Solution: Double-check the spelling of the user name and the
password. Make sure the user and password have been set up on the
remote server operating system.
Inspect the user’s account information on the server. Make sure the
operating system is not expecting the user’s password to be changed
at the next logon. Make sure the user is not also a member of a group
that has restricted permissions.
For Windows NT/2000, be sure that the user is set up as a local user
on the system, not a network user. Network users have a domain
name and a backslash preceding the user name, such as
BOSTON\GILBERT. Be sure that the user who is a member of the
Administrators group or Pervasive_Admin group is a local user.
When trying to create a stored procedure in PCC, I get this
error: ODBC Error: SQLSTATE = S1000, Native error
code = -4994. The record has a key field containing a duplicate
value (Btrieve Error 5)
A stored procedure already exists with the same name as the one you
are trying to create.
Solution: Change the name of the stored procedure. Sometimes
when you create a procedure with a SQL statement, you may not get
a message from PCC confirming that the statement was successful.
Then, when you run the statement again, thinking that it was not
created, you receive this error code. To find out whether or not the
procedure was actually created, you can get a list of the defined
stored procedures by running this statement: select * from
X$proc#
9-11