I run 16- and 32-bit applications on my Windows 95 laptop and they both need to access the same databases. Is there any way to allow the 16- and 32-bit applications to talk to the same local SQLBase server?
Before SQLBase for Windows 95 became available, the local 16-bit SQLBase engines (DBWSERVR.EXE and DBWINDOW.EXE) were fairlystraightforward and easy to get up and running. The database engines and the applications were both 16-bit and they were aware of each other in that the server would launch automatically when needed.
With SQLBase for Windows 95 (DBNT1SV.EXE), there are a few more considerations to take into account:
- SQLBase for Windows 95 is a 32-bit server, which means it can address more memory that was possible with the 16-bit engines.
- 16-bit applications can only connect to SQLBase for Windows 95 via the 16-bit WinSock TCP/IP DLLs.
- SQLBase for Windows 95 does not launch automatically upon database or server connection requests from 16-bit client applications.
There are several ways to do this operation, but the steps listed in this document are the most streamlined based on the information available at the time this document was published.
If you have already installed TCP/IP on your Windows 95 machineand it is working properly, use the steps in this section to configure SQLBase. The following steps assume you are familiar with SQLEdit; (if you aren’t, please refer to the SQLBase Starter Guide):
- Use SQLEdit to configure the Windows 95 Server ([dbnt1sv]) to support both Anonymous Pipes (SQLAPIPE.DLL) for 32-bit client applications and WinSock TCP/IP (SQLWSOCK.DLL) for 16-bit client applications. Additionally, set the server name to be “LOCAL32”.
- Use SQLEdit to configure the Windows 95 client ([win32client]) to connect with Anonymous Pipes.
- Use SQLEdit to configure the Windows 3.X client ([winclient]) to connect with TCP/IP (WinSock). Additionally, you need to set the serverpath parameter value to “LOCAL32,localhost/*”.
- Launch SQLBase Server for Windows 95.
- Now you are ready to connect to the server from either the 16- or 32-bit versions of SQLTalk for Windows.
If you have not installed TCP/IP, use the following steps toconfigure TCP/IP for Windows 95:
- From the Network dialog (accessed via the Control Panel), press the Add button. The Select Network Component Type dialog is displayed.
- Select Network Component Type; select Protocol and press the Add button. The Select Network Protocol dialog is displayed.
- Select Network Protocol; select Microsoft as the Manufacturer and TCP/IP as the Network Protocol and press the OK button. The Select Device dialog is displayed.
- Select Device; If you don’t have a NIC in your PC, select Microsoft as the Manufacturer and Dial-Up Adapter as the Model. Otherwise, select the Manufacturer and Model for the NIC that is installed and press the OK button. The Network dialog is displayed again with the currently installed network components.
- Network; If you are performing this install so that you can communicate with a local 32-bit SQLBase engine, it is important to note that the only components that are required are Dial-Up Adapter and TCP/IP. To remove unnecessary network components, select any of the components you wish to exclude and press the Remove button.
- Network; Once you are satisfied with the installed network components, press the OK button. At this point you may be prompted to insert the Windows 95 distribution media. Once the changes have been made, the System Settings Change dialog will be displayed.
- System Settings Change; Pressing the Yes button will restart your computer with the new network settings.
- After the computer resets, complete the SQLBase and SQLTalk configuration steps as listed above.