SMS uses the Borland Database Engine (BDE) to power the lookups, reads, and writes from the database. The location of the BDE files is found by looking the path up in the registry (Window's internal database). If this information is not found, SMS will not be able to load the BDE and the user will get the following error message:

In order to ensure all SMS clients are using the same version and information, they should all point to the same BDE files.

This process involves modifications to the internal Windows registry. Improper actions in the registry can result in corruption of Windows and crash the system permanently. Be very careful in all interactions within the registry.

This process is usually done:

1. When manually installing a client machine.
2. When a server swap has occurred to manually redirect client machines to the new server rather than reinstalling. (Note that the shortcuts must also be redirected.)
3. When the local client has problems with its registry
4. When another program has overwritten the settings.

1. Navigate to the Registry
   • Click on Start
   • Click on Run
   • Type in regedit and hit Enter
2. Navigate to HKEY_LOCAL_MACHINE>Software
3. Locate the sub-key called Borland. If it is not there create a new key under Software using the following steps:
   1. Right-click on Software
   2. Choose New … Key.
   3. Enter the name Borland for the key and hit the Enter key.
   4. Create new key under Borland called Database Engine, following the steps above with Database Engine
4. Click on the Database Engine key on the left panel. In the right panel, check for the DLLPath value. If it is not there, create a new String Value under Borland using the following steps:
   1. Right-click on Database Engine
   2. Choose New … StringValue.
   3. Enter the name DLLPath and hit the Enter key.
5. Check that the value of the DLLPath is set correctly. For the local server, the path should be C:\Program Files\Cyrious\Common\BDE. For clients, the path should be \\\Cyrious$\Common\BDE where is replaced with the Windows name of the server. If the DLLPath is not set correctly, change its value as follows:
   1. Double-click on the DLLPath value in the right panel.
   2. Enter or replace the value with the correct path.
   3. Click OK.
6. Click on the Database Engine key on the left panel. In the right panel, check for the ConfigFile01 value. If it is not there, create a new String Value under Borland using the following steps:
   1. Right-click on Database Engine
   2. Choose New … StringValue.
   3. Enter the name ConfigFile01 and hit the Enter key.
7. Check that the value of the Configfile01 is set correctly. For the local server, the path should be C:\Program Files\Cyrious\Common\BDE\IDAPI32.CFG. For clients, the path should be \\\Cyrious$\Common\BDE\IDAPI32.CFG where is replaced with the Windows name of the server. Note that this is the same path at the DLLPath but has a filename appended to the end of it. If the ConfigFile01 is not set correctly, change its value as follows:
   1. Double-click on the DLLPath value in the right panel.
   2. Enter or replace the value with the correct path.
   3. Click OK.
   4. Restart the SSLIP and SMS. If the problem persists again reboot the server (the BDE can remain hung unless you do so) and then restart the SSLIP and SMS.

1. Shut down Cyrious on the Server (not the SSLIP, just the SMS.exe)
2. Attempt to open Cyrious on the client
3. If this work, tell them that they can open up Cyrious on the server
4. Inform the customer that Windows 7 OS uses a sandbox to protect the computer from users and if they open it on the server first, they will get this error. Also, if they shut down Cyrious on a client and the server is running, they will have to shut it down on the server to restart Cyrious on the client machine.
5. Explain that there is a fix in the next version - 8.9 (not releasable to Fastsigns stores)

1. Navigate to the Registry
   • Click on Start
   • Click on Run
   • Type in regedit and hit Enter
2. Navigate to HKEY_LOCAL_MACHINE>Software>WOW64Node
3. Locate the sub-key called Borland. If it is not there create a new key under Software using the following steps:
   1. Right-click on WOW64Node
   2. Choose New … Key.
   3. Enter the name Borland for the key and hit the Enter key.
   4. Create new key under Borland called Database Engine, following the steps above with Database Engine
4. Click on the Database Engine key on the left panel. In the right panel, check for the DLLPath value. If it is not there, create a new String Value under Borland using the following steps:
   1. Right-click on Database Engine
   2. Choose New … StringValue.
   3. Enter the name DLLPath and hit the Enter key.
5. Check that the value of the DLLPath is set correctly. For the local server, the path should be C:\Program Files\Cyrious\Common\BDE. For clients, the path should be \\\Cyrious$\Common\BDE where is replaced with the Windows name of the server. If the DLLPath is not set correctly, change its value as follows:
   1. Double-click on the DLLPath value in the right panel.
   2. Enter or replace the value with the correct path.
   3. Click OK.
6. Click on the Database Engine key on the left panel. In the right panel, check for the ConfigFile01 value. If it is not there, create a new String Value under Borland using the following steps:
   1. Right-click on Database Engine
   2. Choose New … StringValue.
   3. Enter the name ConfigFile01 and hit the Enter key.
7. Check that the value of the Configfile01 is set correctly. For the local server, the path should be C:\Program Files\Cyrious\Common\BDE\IDAPI32.CFG. For clients, the path should be \\\Cyrious$\Common\BDE\IDAPI32.CFG where is replaced with the Windows name of the server. Note that this is the same path at the DLLPath but has a filename appended to the end of it. If the ConfigFile01 is not set correctly, change its value as follows:
   1. Double-click on the DLLPath value in the right panel.
   2. Enter or replace the value with the correct path.
   3. Click OK.
   4. Restart the SSLIP and SMS. If the problem persists again reboot the server (the BDE can remain hung unless you do so) and then restart the SSLIP and SMS.

If the BDE is not configured correctly you may encounter an error stating Failed to Open Database. Please reboot your computer. Rebooting will reinstall BDE settings on your machine. If the problem persists and you still cannot access SMS please call Technical Support so a technician can verify that your BDE settings are up to date.