- Installation
and setup
- General issues
- Accounting
packages
- How do I...
- Older
issues (not relevant to current KVS versions)
KVS relies on the Microsoft-recommended function
to detect SQL servers running in the network. Unfortunately, this
function can become confused for a number of reasons. In addition,
various versions of SQL Server install with different security and
network options.
First, problems may occur if the client was
started from hibernation or suspend-mode. You can try re-booting the
client and the server. If this doesn't help, try the following:
- Check that your SQL Server really is running.
- Click the "+" button next to the database
dropdown, and type in the name of the computer you wish to connect to.
This computer will be added to the dropdown list, and you can then
select it.
- If you are installing KVS in a Workgroup ( as
opposed to a Domain), try the following two steps:
- Ensure that the "guest" account on the
server is enabled
- Ensure that the directory with the database
files is shared, and that the clients have access to this directory
- Check the SQL Server network configuration. The
entries for "named pipes" and "TCP/IP" should be enabled.
- Check the SQL Server security settings. Either
"Windows authentication" or both Windows and SQL server authentication
should be enabled.
Yes, KVS works fine with Windows Vista.
However, Microsoft Vista is incompatible with most versions of
Microsoft's own SQL Server. If you want to install SQL Server under
Vista, you will require SQL Server 2005 with service pack 2 or
later.
KVS is compatible with SQL Server 2005, and also with the free SQL Server 2005 Express. However, SQL Server 2005 includes a number of changes that break
backwards compatibility. KVS cannot communicate with SQL Server
2005.
To fix this problem, Microsoft has created a
backwards-compatibility update for SQL Server 2005. This update must be
installed on each client, in order to allow KVS to work with SQL Server
2005. (If you wish to read the technical FAQ from Microsoft,
visit this link: DMO-FAQ.)
Getting and installing the update:
- The update is part of the
Feature Pack for Microsoft SQL Server 2005, called "Microsoft
SQL Server 2005 Backward Compatibility Components. Download the
appropriate package for your clients (most likely the "X86 Package").
Here is a direct download link
SQLServer2005_BC.msi.
- When you execute the installation file, you
will see that it includes four different components. For KVS, you only
need the "SQL DMO" component, however, it may be simplest just to install
everything.
Once this update has been installed, KVS is fully
compatible with SQL Server 2005.
Microsoft Windows does not check the entries in
your regional options - it is possible to have conflicting entries for
the decimal separator, time separator and date separator. Indeed, you
can enter complete nonsense!
Furthermore, a newly installed version of Windows
XP may not correctly save your settings. If your entries appear to be
correct, but KVS still reports a problem, go to the Regional Settings,
change all of the entries, save them, change them back, and save them
again.
These separators are important for KVS. For
example, you can enter durations for events either as a number of
lessons (e.g. 1.5) or as hours and minutes (e.g. 1:30). KVS recognizes
what you mean by looking at the separator character.
We make the following recommendations:
- Separators should be exactly one character in
length. Be careful that there is no "space" before or after the
character you enter.
- Currency and decimal separators should be
identical.
- Currency and decimal grouping symbols should be
identical, and should be different from the separator character.
- Decimal, time and date separators should all be
different from one another.
Note: earlier versions of KVS (through
3.3) required you to have different separator
characters. as of version 3.4, KVS does the best it can with whatever
entries you have chosen.
You have created a new record in an edit-register,
and have not yet saved it. When you try to delete the record, you
receive an error message that the data in the record is incorrect, and
you cannot delete it.
There are two causes of this error:
- The data in a particular field is
invalid. This behavior is by design - Each field of a record
is checked for validity before the mouse is allowed to move to another
field. Hence, in order to move the mouse away from the field (e.g., to
the delete button), the current field must contain valid data. Enter
valid data in the field, then delete the record.
- The data in the individual fields is
correct, but the combination is invalid. Example: you have
entered a semester where the end-date is before the start-date. In this
case, you can delete the record by clicking in the left-hand margin to
highlight it, and then pressing the delete key.
Situation:
You use Outlook 2002. When you attempt to send e-mail using KVS, you
receive an error message.
- Diagnosis:
The libraries installed with Outlook 2002 prohibit programs from
sending e-mail through the standard MAPI interface without your
explicit approval. However, if Outlook 2002 is not running, it cannot
ask for your approval.
- Solution: Leave
Outlook running while you are using KVS. When KVS attempts to send
e-mail, Outlook will ask if you want to allow KVS to send e-mail on
your behalf.
Situation:
You use Outlook Express. When you attempt to send e-mail using KVS, you
receive an error message.
- Diagnosis:
Outlook Express does not, by default, register itself as your standard
e-mail program.
- Solution: See
Microsoft
KB article 178077 for the solution to this problem.
For many reports, it is useful to look at a period
in the future - for example, which events is a student scheduled to
attend next month? However, when you attempt to set the start date, you
receive the error message that the date cannot be later than today.
The reason for this is that, when you first open
an event report, both the start date and the end date are set to today.
This gives you a report containing today's events.
You cannot set the start date later than the end
date. So - if you want a report for a future period - you must first
change the end date. After changing the end date, you can then set the
start date.
When you type in a dropdown lists, you expect the
list to "auto-complete", that means, to move to the first entry that
matches what you have typed.
There are two types of dropdown lists in KVS: ones
that are part of a form (such as the "gender" dropdown you see when
entering a new person), and ones that are embedded in tables.
The dropdowns that are embedded in tables only
"auto-complete" correctly if you first open the dropdown list by
clicking on the arrow.
This error was eliminated as of KVS 4.0.16.
During data entry, you are entering data in the
tabs at the bottom of a window, for example, the "address", "personal",
and "info" tabs of an individual. The error occurs when you enter data
into a field on one tab and then click on the tab-list to select a
different tab. When you save the record, the information in the last
field on the previous tab is not saved.
We have traced this error to a problem in the
Microsoft controls (Microsoft article
Q197128). Microsoft has documented the error, but has not
fixed it.
If you are using KVS 4.0.14 or earlier, there is
a simple workaround: after entering data in the last field on a tab,
but before changing to another tab, click somewhere - on any other
field on the form - anywhere but the tab-list. Your data will then be
saved correctly.
Versions of KVS beginning with KVS 4.0.15 work
around this problem, and no special action is required on your part.
When you use the meeting and event markers in an "invoice
letter", each meeting or event should display on a separate line.
However, they do not - instead, they are all on a single line,
separated by a "box" character.
- Diagnosis:
This is an error in Microsoft Word, in particular, Office 2000
(see Microsoft article Q274134). We have also seen this error
with Office 2003. The error occurs when an automated
search-and-replace is performed in a table.
- Solution: Do not place meetings and events
inside of a table.
We have developed interfaces for several versions
of QuickBooks. Please note, however, that every single version of
QuickBooks requires a different interface.
If you wish to use QuickBooks, please contact us
for further information.
Although KVS can communicate with this
package, we do not recommend it. The Sage KHK API is not reliable, and
we have discontinued support for this package.
1. Where do I find the client
installation?
Sage KHK does not provide a client installation.
You must install the full accounting package (and purchase a license)
on every single computer.
1. Where do I find the client
installation?
On your Sesam CD, or just download the appropriate
component here:
Client Component for SESAM
Version 4 (530KB)
Client Component for SESAM
Version 5 (4.4MB)
2. Sage SESAM - must be Power User or
Administrator
Situation:
When you try to run KVS with Sage-SESAM, you can only do so as a
power-user or an administrator.
Diagnosis:
This occurs because a sub-component of Sage-SESAM is trying to add
entries to a log-file, and the log-file is stored by default in a
protected directory. We believe that this problem is limited to
Sage-SESAM version 4.x. To correct this problem, you must change the
following entry in the Registry:
HKEY_LOCAL_MACHINE
SOFTWARE
Btrieve Technologies
Microkernel Workstation
Version 6.15
Settings
Home Directory : REG+SZ: C:\WINNT
Solution:
Change the directory specified to one where all KVS users have write
permissions.
Printing the reports you just generated by
clicking on "Save all" is easiest using Word. Open Word, then open the
Word document browser. Find and select the reports you want to print.
Then click on the dropdown "Tools" and select print. Word will print
all the selected documents without any prompting.
Note: KVS no longer uses MSCAL.OCX.
When you try to install KVS, you receive an error
message similar to "DllRegisterServer in C:\WINNT\system32\MSCAL.OCX
failed." This can occur when your system has Version 5.0 of COMCAT.DLL
installed. The problem can be resolved by manually
replacing this with the older version 4.71.1460.1
of COMCAT.DLL. This is the version delivered with KVS.
Unfortunately, the KVS installation routine cannot
do this for you - installation procedures should never replace newer
versions with older versions! For further information about this
problem, please refer to Microsoft Knowledge Base article Q247649.
|
