|
|
Frequently Asked Sales Questions
This page contains answers to many common questions fielded by our sales staff. If you have a question that isn't answered here, feel free to contact us by email, fax or phone.
General Questions
-
Which version of CodeBase is right for me? Which version of CodeBase is right for me? Which version of CodeBase is right for me?
CodeBase is available for most development platforms. Use our CodeBase Product Comparison chart to help determine which version is right for you.
-
What's the difference between networked multi-user and client/server?
Both networked multi-user and client/server applications support multiple users accessing shared data files concurrently. The difference is in the way the applications access the data. In networked multi-user applications, each application explicitly opens the required tables and performs multi-user sharing through the placing of file/record locks. The application is self-contained, in that it contains all the needed functionality to manipulate tables directly.
In CodeBase client/server, applications never open tables directly. They do not contain the logic require to perform these actions. Instead they contain logic to request the CodeBase server to open a table on their behalf and return the results.
The advantages of both networked multi-user and client/server are discussed in the topics What are the advantages of using CodeBase client/server? and What are the advantages of using CodeBase standalone?
-
How does CodeBase compare to products like SQL Server?
While CodeBase and products like SQL Server both offer database management capabilities, they are quite different in many fundamental aspects. The following table provides a list of product attributes comparisons that help highlight their similarities and differences:
| Product Feature |
CodeBase |
Microsoft SQL Server 7.0 |
| Read, Write & Create data files |
Yes |
Yes |
| Query data files |
Yes, using xBASE expressions |
Yes, using SQL |
| Database Storage |
Individual Tables. xBASE Format (.DBF) |
One Database. Proprietary format |
| Maximum Database Size |
4.2 billion gigabytes.
More...
|
4 terabytes for entire database |
| Standalone support |
Yes. Local and networked multi-user |
Local only. Low performance |
| Client/Server support |
Yes |
Yes |
| Support SQL |
Yes, via ODBC driver |
Yes |
| Transaction Support |
Yes |
Yes |
| Typical system requirements |
1 MB RAM
350 - 950K disk space
Windows XP, 2000, NT, Me, 98, 95, 3.x or DOS |
32 MB RAM
170 MB disk space
Windows NT Server |
| Embeddable into standalone .EXE |
Yes |
No |
| Referential Integrity |
Can be done programmatically |
Yes |
| Replication |
Can be done programmatically |
Yes |
| Licensing |
Per developer |
Per installation |
| Cost per developer |
$ 395 |
N/A |
| Cost per distribution (10 users) |
$ 0 |
$ 1999 (approximate street price) |
| Source code included. |
Yes |
No |
| Server source code available |
Yes |
No |
| Supported Operating Systems |
Windows, UNIX, Linux, Mac, Dos, OS/2 |
Windows |
-
Can you use CodeBase with MS Access?
Yes. Using our included Visual Basic support, you can call the CodeBase DLL from Access projects. Optionally you can also use CodeBase from Access using CodeBase SQL-ODBC.
-
Is CodeBase a plug-in replacement for Jet?
With our ODBC Driver or ADO Provider add-on, it can be, but it depends on the data access method you are using, and which features of the data access method you invoke. For example, certain DAO properties and methods are only available when used in conjunction with Jet (Refer to VB help on DBEngine for more information). CodeBase tables and Jet databases are not compatible, so you also need to convert your Jet database into CodeBase tables. This can be accomplished with a Visual Basic program. If you want to take advantage of the superior speed of the CodeBase low-level API, you will need to convert your existing data access code to the CodeBase API.
-
Is CodeBase a plug-in replacement for the BDE?
CodeBase by itself is not a plug-in replacement for the BDE. However, with the
CodeBase
Components add-on product, CodeBase becomes a true plug-n-play
replacement for the BDE.
-
What are the advantages of using CodeBase client/server?
Client/Server computing offers four main benefits over standalone models:
- Stability - If a client machine crashes or gets
disconnected from the server, other users are not affected, and there is little chance of
database corruption.
- Security - By securing access to the database server
computer, you secure access to your data, as the CodeBase server enforces user logon and
file access security.
- Performance - In situations where data files are large,
client/server can boost performance by executing queries on the server, and then returning
only a small result set to the client. This speeds performance and significantly reduces
network traffic.
- Workload Sharing- When you run a client/server
application in essence you have two computers working on a single task. This sharing of
the workload reduces the performance requirements for both machines, and in the case where
the server machine is more powerful, adds significant processing power to each client,
resulting in an excellent hardware cost-to-performance ratio.
-
What are the advantages of using CodeBase standalone?
Using CodeBase in a standalone configuration offers the following benefits:
- Smaller distribution and simpler setup - The CodeBase
standalone libraries require a smaller disk footprint than the CodeBase client/server
configuration. Also, with standalone you can either embed CodeBase directly into your
applications (C/C++), or at most distribute a single DLL.
- Better for local computing - In situations where your
application is running against data files on a local drive, standalone offers better
performance, as there is no need for the overhead of client/server communications.
- Performance - In situations where you are skipping
through moderate to large portions of the database, using standalone offers better
performance in both local and networked multi-user scenarios.
-
What 3rd party tools does CodeBase work with?
If you use CodeBase SQL, you can use CodeBase with virtually any tool that supports ODBC.
Technical Questions
-
What file formats does CodeBase support?
CodeBase supports the data, index and memo files of FoxPro 2.x and above, dBASE IV and above and Clipper Summer 87
and above. File compatibility is summarized in the following table.
xBASE File Extensions Supported
| |
Table |
Index |
Memo |
xBASE Version Supported |
| Fox |
.DBF |
.CDX |
.FPT |
2.x and higher |
| dBASE |
.DBF |
.MDX |
.DBT |
IV and higher |
| Clipper |
.DBF |
.NTX |
.DBT |
Summer '87 and higher |
-
How is CodeBase integrated into my application?
CodeBase can be used as either an embedded library or a DLL, depending on which programming language
you use. The following table shows the available distribution options:
Programming
Language |
Distribution Options |
| C/C++ |
CodeBase embedded directly into your application
or your application dynamically linked into the CodeBase DLL |
| Delphi |
Dynamically linked |
| Java Client/Server |
Embedded directly into your Java application |
| Java Standalone |
Dynamically linked into CodeBase DLL (Windows) or Shared Library (UNIX) |
| Visual Basic |
Dynamically linked |
-
How much size does CodeBase add to my distribution?
The size of the CodeBase distribution depends on which xBASE format you are using, and whether your application is standalone or client/server.
Disk Footprint:
| Windows |
|
Standalone |
400K |
| |
|
Client/Server |
client - 300k
server - 650K |
| |
|
|
|
| Windows CE |
|
Standalone |
180K |
| |
|
|
|
| Java |
|
Standalone |
475K (varies by OS) |
| |
|
Client/Server |
client - 75k
server - 650k |
Note: Disk footprint can be reduced further by recompiling provided source code with CodeBasecode-reduction compilation switches.
Memory Footprint:
Minimal startup requirements. Mainly dynamic allocation, which is entirely dependant on size and number of tables/indexes in use. For optimal efficiency, size and number of memory allocation pools can be configured at design or run-time.
-
Is CodeBase multi-user compatible with my legacy xBASE applications?
Yes. CodeBase uses the native locking protocols for FoxPro, dBASE and Clipper, so that CodeBase applications can run concurrently with existing xBASE applications against the same data files.
-
Does CodeBase support BLOBs?
Yes. You can use Memo fields to store any kind of information, including binary data such as images. 32-bit
CodeBase applications can store up to 4GB of data per memo entry. As an alternative, you can simply store references
to images files in the database. This provides you with access to the images from other programs and utilities.
-
Do you need a Windows XP/2000/NT Server/Workstation to host the CodeBase database server?
No. The CodeBase server can also run on a Windows Me, 98, or 95 workstation, making it ideal for both large and small networks.
-
Does CodeBase support SQL?
Yes, through our CodeBase SQL product which supports ADO, ADO.NET, ODBC, and ODBC.NET.
-
Which UNIX versions are supported with CodeBase?
CodeBase is tested under a variety of UNIX platforms. In addition, we offer to support any platform that we haven't specifically tested on, providing that you allow us to Telnet into your system in order to test CodeBase. The specific Unix systems that we have tested under are:
| Non-Intel UNIX |
Intel-based UNIX |
AIX
Dec Alpha
HP-UX
IRIX
Solaris
SunOS
|
BSDI
DGUX
Linux
SCO
Solaris x86
Unisys
UnixWare
|
-
Which devices does CodeBase for Windows CE support?
-
Does CodeBase work on Novell networks?
Yes. You can host and run CodeBase applications that are hosted on Novell drives, and you can access CodeBase
tables that are located on Novell drives. CodeBase does not come as an NLM (Network Loadable Module) however.
Pricing/Licensing Questions
-
What is the CodeBase Pricing model?
CodeBase is sold on a per-developer basis, meaning you must purchase a copy for each developer who will be working with CodeBase source code, libraries, etc. After development, there is nothing else to pay for distribution of the applications you create with CodeBase. You can contact our Sales department for special pricing on site licensing for multiple developers.
-
Can I distribute the CodeBase database server royalty free?
Yes. When developing client/server applications, you can distribute the CodeBase 10 concurrent-user database server royalty free. If you need to distribute a CodeBase server that can accommodate more than 10 concurrent users, you can purchase server upgrades for either a single-site installation, or unlimited distribution. See our order page for pricing information. Also, refer to the server upgrade question.
-
Can I install CodeBase on more than one computer when developing my applications?
Yes. However, if more than one developer will be using CodeBase, each must have their own copy, or you must own a site license.
-
Where can I locate resellers in my country?
In North America you can order directly from Sequiter Software Inc. For other countries, refer to the Reseller links.
-
Does purchasing the CodeBase server source code change my distribution licensing?
No. When you buy the CodeBase server source code, your CodeBase server distribution rights don't change. For example, if you purchase CodeBase 6.5, which includes licensing for distribution of a 10 concurrent-user server, and you also purchase the server source code, you can modify the server source and distribute the resulting executable under the same 10 concurrent-user restriction only. If you want to allow more connections on the modified server, you would also need to purchase a server upgrade license for the required number of users/installations.
-
On your price list, you have items such as 20-user server one-install. What are these
items?
These are the licensing upgrades you can purchase for CodeBase client/server. The base CodeBase package includes an unlimited-distribution 10 concurrent-user license, and these upgrades can be used to supplement that license. For example, if most of your CodeBase client/server installations require 10 or less users, but one site requires 11-20 users, you can upgrade to a '20-user server one-install', which provides you with a license to install one instance of a 20-user CodeBase server. If your needs require many 20-user servers, purchasing the royalty-free 20-user version could save you a significant amount of money.
Upgrade Questions
-
Is the CodeBase 6.5 API the same as the 6.x API?
Yes. The CodeBase API has remained the same from 6.x through to 6.5. If you have existing 6.x applications, you should simply be able to recompile in most circumstances in order to upgrade your applications from 6.x to 6.5.
-
What are the main differences between my older version of CodeBase and CodeBase 6.5?
Every new CodeBase sub-release has a common set of features, which usually includes improved performance, updated compiler support, etc. In addition, the following table shows other major features added in each CodeBase 6 sub-release:
| Version |
Major new features added |
| 6.5 |
Unicode (C, C++, Delphi) |
| Visual FoxPro field support |
| Large File Support |
| 6.4 |
Performance Improvements, especially under Client/Server |
| Client/Server security added. Logon and
file permissions supported. |
| New administration tools for client/server |
| Windows 98, NT4 support |
| CodeReporter upgraded to 32-bit |
| Royalty-free client/server upgraded to 10 concurrent-users (Patch) |
| 6.3 |
Performance Improvements |
| Long file name support |
| CodeControls 3 (32-bit ActiveX data-aware controls) |
| 6.2 |
Performance improvements |
| Updated file support for latest versions of FoxPro, dBASE, Clipper |
| 6.1 |
Performance improvements |
| Java support |
| 6.0 |
Performance improvements |
| Client/Server support |
| Cross-language support for C, C++, VB and Delphi |
| Transaction Processing and Logging |
| 32-Bit support |
| Windows 95 and NT 3.5 support |
|
|
