| Sort by:
|
Page 2 of 7 | Previous | 1 2 3 4 5 6 7 | Next
|
|
|
24 Jul 2000
|
Connecting to the InterBase server displays the Dial-up Connection dialog
A couple different solutions to this problem
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
connection rejected by remote interface
InterBase is not certified for a v5 client to talk to a v3.3 server.
|
Borland Staff
|
FAQ
|
|
|
|
|
12 May 2004
|
Converting the trial install into a server install
Before InterBase 7.1, it was quite easy to convert the trial to a full server install. Now it isn't so easy.
|
Quinn Wildman
|
FAQ
|
|
|
|
|
29 Mar 2001
|
Custom installation of Interbase 6.0
My installer for Interbase 6.0 gets an error during installation, "Unable to Copy File".
|
Justin Swett
|
FAQ
|
|
|
|
|
14 Jul 2003
|
Deadlock errors: cause and resolution
What causes deadlock errors and how to handle them.
|
Ben Matterson
|
FAQ
|
|
|
|
|
24 Jul 2000
|
Distributing InterBase databases on CD
I need to distribute a database on CD. Is this possible with InterBase?
|
Borland Staff
|
FAQ
|
|
|
|
|
16 Feb 2005
|
Documentation for RDB$USERS
RDB$USERS is new system table introduced in InterBase 7.5
|
Quinn Wildman
|
FAQ
|
|
|
|
|
24 Jul 2000
|
Does InterBase set the remote buffer size?
For Interber 5.0., 5.11 is is hard coded. It is configurable in later versions.
|
Borland Staff
|
FAQ
|
|
|
|
|
21 Jul 1999
|
Embedding InterBase 6.0 in 10 easy steps--InterBase Install and Licensing APIs
InterBase 6 has a new install API that automates many chores involved in embedding the database into an application. This session describes the API and how to use it.
|
Borland Developer Support
|
White Paper
|
|
|
|
|
24 Jul 2000
|
Error Message: statement failed -902 operating system directive semget failed.
Increasing the system available sephaphores may resolve the problem
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
Error Message: statement failed sql code -104, lock manager out of room
Increasing shared memory may resolve the problem
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
Error: cannot format message 14:0, message text not found
Possible causes:<ul><li>Improper installation of a new kit when previous version kit exists</li><li>Interbase.msg file is corrupted.</li><li>Wrong interbase.msg file (because of situation described above</li></ul>
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: inconsistent lock table version number
Possible cause is an application that was compiled or linked with another version of InterBase, one that had a different lock table version.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: invalid lock id() errno=??
The meaning of this error isn't always the same.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: Semop failed, errno=22
This error is due to running out of semaphores or shared memory.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: Semop failed, errno=28 [-no space left on device]
This error is due to running out of semaphores or shared memory.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
Features of the evaluation licenses
Evaluation licenses have limited lifetime and limited features
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
General Information on error number 146
5 possible causes for error 146.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
getting error "I/O error for file: printer out of paper" when using NT
There are two known problems:<ul><li>System is running out of temp space</li><li>The environment variables TEMP and/or TMP have not been defined.</li></ul>
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
Getting Error: fatal lock manager error -semop failed (acquire) errno 28
This error occurs when the InterBase tries to acquire semaphores for use with<br>the lock table and the operating system returns an error.
|
Borland Staff
|
FAQ
|
|
|
Connect with Us