|
If you install the AppForge development environment after you have installed UltraLite, the utility registers either the UltraLite runtime or the UltraLite Engine client, so that the AppForge development environment contains a reference to the appropriate UltraLite namespace. These changes allow the load AppForge type libraries to be loaded. You can also unregister these *.DLL files with this utility.
ulafreg [ options ]
| Option | Description |
|---|---|
| -d |
Display the location of the currently installed version of AppForge. |
| -q |
Set the utility to run in quiet mode. Suppress informational banners, version numbers, and status messages. Error messages are still displayed, however. |
| -r [ directory ] |
Register the UltraLite runtime *.DLL in named directory (for example, ulmvb10.dll). Only one application can reference this file. If you do not set directory, the default SQL Anywhere installation location is assumed (that is, install-dir\ultralite\UltraLiteForAppForge\win32\). |
| -rc [ directory ] |
Register the UltraLite Engine client component *.DLL in named directory (for example, ulmvc10.dll). Multiple applications can reference the same registered engine client *.DLL file. If you do not set directory, the default SQL Anywhere installation location is assumed (that is, install-dir\ultralite\UltraLiteForAppForge\win32\). |
| -u |
Unregister the UltraLite AppForge component. The 10.0 UltraLite for AppForge component replaces previous versions of UltraLite for MobileVB. You cannot use more then one version of the component on the same machine. Therefore you must unregister these previous version before registering an UltraLite for Appforge 10.0 component. |
ulafreg is a Windows executable.
Once the executable has ended, click the Edit > Copy to copy the information in the Window.
Paste the output in a text editor of your choosing.
Save the output to any desired location.
If you are unsure whether or not you need to run the utility, follow the procedure described below.
Do one of the following:
Check that a new project includes a reference to an UltraLite-specific namespace.
Check if the correct connection class (for example, ULConnectionParms) appears in the AppForge list of available classes.
If it does not, close AppForge.
Run the ulafreg utility with the appropriate options.
Restart AppForge.
If you run ulafreg in a regular session with administration privileges, Vista displays its output in a new console window, that is immediately discarded when the ulafreg command ends. You cannot view the results of the utility if this occurs. To avoid this behavior, follow the procedure below.