Q: What should I do if I think I have found a defect in the OGWin software?

A: Email the support staff at support@ogsys.com with detailed information about the bug so we can reproduce it and fix for future releases!

Q: What does it mean when I get an "error -132" when upgrading OGWin?

A: This means that the Pervasive engine is still running and a file copy failed. Make sure all users are logged out of Ogwin and attempt the upgrade again.

Q: What does it mean when I get an "error -115" when installing OGWin to a server?

A: An error -115 means that a file is in use, therefore it could not be copied over, or you do not have access to the directory you are trying to install OGWin to at the server. First verify everyone is out of the system. Then try installing OGWin again. If you still receive the error, check with your network administrator and verify you have full access to the directory you are installing to.

Q: Should I install OGWin at the server or from a workstation?

A: OGWin installations and upgrades should always be done from the workstation, whether you are installing to the server or as a single station. The Ogwin installation tests for user rights and path problems.

Q: Why can't I see the bottom of the screen on OGWin applications?

A: This is most likely caused by the user using a video driver setting that is less than 800 X 600. OGWin does not support video drivers less than 800 X 600 large fonts. Go to Start; Settings; Control Panel/Display settings tab and change the display to 800 X 600 or larger.

Q: Can the windows in OGWin be made bigger?
A: Yes. Report screens as well as search screens can be expanded to view more items.

Q: How do I unlock a locked database?

A: First, verify with the OGWin support staff that your database has not been corrupted or that the problem that caused the database to be locked has been remedied. After this has been done sign on to the locked database as Supervisor. Click on OK to the locked database message. Go to Supervisor/Ogsys Maintenance. On the Ogsys Maintenance screen click the unlock database button (the button is disabled if the database is not locked). Note! Always check with the staff at OGSYS before unlocking the database so the problem can be diagnosed. You will be asked by OGSYS support staff to send the Ogwin\program\site\admin.ctl file. This file will help in troubleshooting the error.

Q: How can I name a station a name already in use by an obsolete station?

A: First you must delete the station name for the old station. Log into OGWin as Supervisor. Go to Supervisor/Station Maintenance, click the button labeled options. Select the name of the station that is old and click delete. After removing the old station name go back to the new computer that you wish to use the name on and rerun OGWin. When the box appears type in the name you wish to call the new station and then start OGWin again.

Q: How can I keep OGWin from Minimizing on its own an requiring a password to Restore?

A: The feature that closes OGWin and locks it in a minimized state is a security feature designed to keep others out of you records while you are away from you desk. To disable this feature login as Supervisor, go to Supervisor/Station Maintenance and click the options button. On the options screen under Task Options, "Minimize and require password when idle for 10 Min", set the minutes field to zero and uncheck the check box at the beginning of the statement. OGWin will no longer Minimize on its own.

Q: What does the error "Wrong version for File ID "file name". Current version is 4.00 and should be at least 6.00. You should use EditMnt to rebuild this file"?

A: OGWin files run better when they are in 6.00 Pervasive format. 4.00 format is an older Btrieve format and needs to be converted to at least 6.00 before OGWin can open the files. To do this; run Ogwin\program\Editmnt.exe with Windows Explorer. Choose the Database system that contains the files that need to be converted, under Repair Mode check Rebuild all Files, under File Selection check All Files, under Index Validation check None. Then click Run. After the rebuild has run you will be able to login into the converted database on OGWin.

Q: How do I set up new users in OGWin?

A: Login in as Supervisor to the OGWin database that you would like to add a new user to. Go to Supervisor/User and Group Maintenance. Under the Users tab click New User, type the users name and password into the fields. You can copy the permissions of a current user by selecting the users name from User to Copy. Click Ok and then close. For these changes to take effect you will have to logoff of OGWin.

Q: How do I set up new groups in OGWin?

A: Login in as Supervisor to the OGWin database that you would like to change or add user and group preferences to. Go to Supervisor/User and Group Maintenance. Under the Groups tab click New Group, type the groups name in the field and choose a Group to model the permissions of the new group by from Group to Copy.

Q: How do I change User and Group Access in OGWin?

A: User and Group access can be set to allow users no access to certain areas of OGWin, Read-Only Access to certain areas or Full Access to the area where changes can be made to the database. Login in to the database you want to change the access on as Supervisor. Go to Supervisor/User and Group Maintenance. Under the User and Group Maintenance tab you will see three windows. The top left window shows all the users on this database. The bottom left window shows all the groups on the database. The right window shows the access rights of the user or group selected. To change the rights of a user or group first select them from the windows on the left. You will then see the access rights for your selection on the right. You will see either a Red X, denoting No Access, a pair of Yellow Glasses, denoting Read Only Access, or a Green Check, denoting Full Access to the particular process. To change the permission of a particular process click the icon representing its current access level until it change to the desired level. You will have to logoff of OGWin and then log back in for the changes to take effect. Note! If a user is a member of a certain group and you change the groups access rights the users access rights will also be changed.

Q: How Do I install Pervasive 2000 to an NT\2000 server?

Installing the Pervasive.SQL 2000 Server Components
You must install the Pervasive.SQL Server for Windows NT\2000 at the server
itself; you cannot install it remotely from a client machine.
To install Pervasive.SQL 2000 (Server Edition) on a Windows NT machine:

1. Launch the installation program from your Windows NT machine.
a. Insert the Pervasive.SQL Server for Windows NT CD in the CD-ROM drive of your Windows NT server.
b. If the installation does not start automatically, click Start, select Run, and type drive:setup where drive is the drive letter of your CD-ROM device. The following dialog box displays.
Pervasive.SQL Setup Welcome Screen
Click Next to proceed with the installation..Installing Pervasive.SQL 2000 on Windows NT.

2. In the Select Product screen, click Pervasive.SQL Server. Select Product Screen Click Next to proceed with the installation

3. Select whether you want to do a typical or custom installation.

Setup Type Screen
The typical installation, which is recommended for most users, takes default actions for most operations performed during the installation. The custom installation lets you choose the components you want to install and specify the program folder name and pervasive.SQL 2000 engine service start mode.

The typical NT server installation installs the following components:
Pervasive.SQL 2000 Engine (including ODBC interface)
All possible requesters (MS-DOS, Win16 and Win32 requesters)
Utilities
Transactional and relational interfaces
Client installation copies
Online documentation.Installing Pervasive.SQL 2000 on Windows NT.
During a custom NT server installation, the following components are
optional:
Online documentation
Network client support
Client install programs for DOS and Windows.
If you choose a custom install, skip now to “Custom Installation Path” on
page 2-14. At the end of that section you will return to this section to continue
the installation.
Click Next to proceed with the installation.

4. Select your installation directory.
The default installation location for Pervasive.SQL 2000 is C:\PVSW,
assuming the Windows system drive is C. You can specify a different location
for the installation as shown in the following dialog box:
Selecting your Installation Directory of Pervasive.SQL.2-10 Getting Started with Pervasive.SQL 2000
If you want to change the default directory, click Browse and select the
desired directory. Click Next to install the Pervasive.SQL files. File copying
will begin at this point. When it is complete, you will register your user count
license key.

5. Copy the Pervasive.SQL server software to your hard disk:
Please wait while the Pervasive.SQL server files are copied.

6. Apply your user count license key:
The Setup User Count License dialog box displays:
Applying the User Count License
Your Pervasive.SQL 2000 server is set to the number of users specified in the
license key. When the update is complete, a dialog box informs you that you
have increased your user count license to support that number of
simultaneous users. At this point, your Pervasive.SQL 2000 transactional and
relational services will be started..Installing Pervasive.SQL 2000 on Windows NT.
Note
If you do not yet have a license key or it is not with you at the moment,
you can still continue with the installation. Click Skip at the Setup
User Count License dialog box and run the User Count Administrator
utility at a later time to install a user count license key. Please wait until
the installation is complete.

7. Perform engine functionality check.
It is recommended that you perform this test to ensure that the transactional
and relational interfaces are communicating properly.
If performing the test, select the samples subdirectory of the server
installation location. This will test the transactional interface.
Functionality Check Screen. Getting Started with Pervasive.SQL 2000
If you performed the test, the following status screen informs you of the test’s
progress:
Testing 32-bit Btrieve Interface Screen
Click Finish. Installing Pervasive.SQL 2000 on Windows NT.

8. Your Pervasive.SQL 2000 server installation is complete.
The following screen informs you that the installation is complete.
Install Complete Screen
It is highly recommended that you leave the View readme file check box
selected.
Click Finish.

Note
If you had any trouble with installation, see Chapter 9, “Troubleshooting Installation Problems.”
If installed files could not be copied because they were locked in
memory, a reboot may be necessary at this point.
The install program modifies the PATH, PERVASIVE_PATH and
CLASSPATH environment variables at the end of the installation
process. These settings control how your Windows operating system
finds Pervasive components. These environment variables are stored in the Control Panel under the Environment tab on the System icon.

top