SOLID Light Client FAQ

SOLID Server version 02.20.0027 or newer.
SOLID Server up, running and listening to the proper tcp/ip port.
- See SOLID Server documentation on how to do this.
TCP/IP working between client and server machines.
- This can be verified using the standard tcp/ip tools (e.g., ping)
A runtime program for sockets properly set up.
- For NT this means:
  - NT's standard tcp/ip DLLs should be loadable.
- For DOS this means:
  - autoexec.bat should load sockets.exe TSR to provide tcp/ip services for Light Client
  - protocol.ini settings should match network numbers and names
  -thetcputils.ini hostname should match the network name
The program really uses a Light Client library, not standard ODBC
- In environments supporting standard ODBC, some development tools link to odbc32.lib, providing standard ODBC services as a default library to any project. Because (most of) the functions have similar names and interfaces, the program may be linked to use ODBC instead of Light Client. Remove odbc32.lib from the linker's file list.
- This problem causes the error: IM002, "Data source not found and no default driver defined", given by the ODBC Driver Manager.

2. Programming Issues

Q2.1. I have an application written in Visual Basic running on SOLID Server . What do I need to do to start using SOLID Server through the Light Client API?

A: You can't do it. Visual Basic implements its own API on top of ODBC. This layer always expects to find a full ODBC below it. This applies also to most other 4GL tools.

Q2.2. I have an application running on SOLID Server through ODBC. What do I need to do to start using SOLID Server through the Light Client API?

A: Please follow these steps:

Review how your application uses ODBC, and estimate whether the Light Client API's set of functionality is sufficient for you. Some minor changes in your own code are to be expected.
Download the SOLID Light Client package.
Verify your environment using SOLID Light Client samples.
Modify your own program's ODBC calls and test your program.

Q2.3 I am running my Light Client Application on DOS. For some time everything seems O.K. Then suddenly, I don't seem to be able to reconnect. What can I do?

A: The problem is the version of sockets.exe DOS TSR that does not always immediately release the socket resources. The workaround for this is to wait a moment after each disconnect. It may be sufficient to avoid taking new connections too often.

The reason the delay is not written inside the Light Client library is that there are versions of sockets.exe around. Some work better in this respect.

3. Runtime Issues

Q3.1. What does 'Light' in Light Client mean?

A: It means that the size of the library is as small as possible. All the functionality that is not absolutely necessary has been stripped. Please check the actual Light Client library sizes for the available platforms from the SOLID Light Client Release Notes.

Q3.2. Are there any SOLID Server administration utilities available for use on the 'Light' workstations?

A: There are no SOLID Remote Control nor SOLID SQL Editor programs (not even the teletype versions) available for DOS clients. However, Light Client programs can be written that pass "ADMIN COMMAND" SQL statements to SOLID Server through the Light Client API. For details, see SOLID Server Administrator's Guide Appendix D SOLID SQL Syntax..

4. Licensing & Pricing Issues

Q4.1. How is the Light Client library priced?

A: There is no separate price for the SOLID Light Client library. You are free to download and use it to connect to SOLID Server according to your license terms.

Q4.2. What kind of license do I need for running SOLID Light Client applications?

A: A normal SOLID Server license is sufficient for running Light Client applications. Light Client connections are counted as normal connections when monitoring the number of concurrent users. Each Light Client connection is counted as one user in the SOLID Server license.