| Sort by:
|
Page 4 of 6 | Previous | 1 2 3 4 5 6 | Next
|
|
|
24 Jul 2000
|
InterBase version 3.3 product releases
Lists all platforms InterBase 3.3 was released on
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Client application doesn't see events if NT Service Pack 2 or 3 is installed
Installing later service pack should resolve the problem
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
When installing BDE based products they overwrite IB v5 gds32.dll with v4.2.1 dl
Rename gds32.dll before and after BDE install to alleviate the problem
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Deploying InterBase v5.0 and why the file msvcrt.dll is needed
Without msvcrt.dll installed gds32.dll will not run.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Error installing from InterBase: String variable is not large enough for strin
Trying to install InterBase 4.2.1 from the JBuilder 1 CD produces error message.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Trying to install InterBase from the C++Builder CD and I dont have ID / Key info
The Certification ID and the Certification Key needed by the setup program are located in the file ibkey.txt in /IB5/ on the CD-ROM.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Installing on SCO failed with error "unrecognized distribution"
The above error is generated because one tries to install SC-V4.0C kit on a SCO 5 machine.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
How big is the Windows InterBase installation foot print?
A full installation is roughly 27908.6 kb.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
What are the system requirements for InterBase v5.x
The suggested system requirements for the shipping versions of v5.x are:
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
What Administration Tools ship with your Windows based Server Product
Note: This information pertains to the InterBase kit for Windows 95/NT.
|
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
|
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
|
ODS Downgrade
Is it possible to downgrade from ODS 9.0 to ODS 8.0?
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Error: cannot format message 14:0, message text not found
If you get this error message in standard output, it normally means one of the following:<BR>a) Improper installation of a new kit when previous version kit exists<BR>b) Interbase.msg file is corrupted.<BR>c) Wrong interbase.msg file; because of issue a
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
The system cannot find the path specified
While trying to run the Database Statistics on a database I get an error.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
ODBC doesn't display time portion of the InterBase date
Can't display the whole date (date & time) via the 16-bit ODBC driver by InterSolv.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Escape clause {oj} fails to function
Escape clause {oj} fails to function since upgrade to ODBC driver version 2.00.903.
|
Borland Staff
|
FAQ
|
|
|
|
24 Jul 2000
|
Registry key that tells where IB looks for the license file
HKEY_LOCAL_MACHINE | Software |InterBase Corp | Interbase| Current Version determines where InterBase is installed
|
Borland Staff
|
FAQ
|
|
|
Connect with Us