Latest
revision history
|
| 6 October |
Various buxfixes: registry problem, error when
several meta dropdowns had the same value, "please
start Outlook manually". |
| 4 September |
Minor bugfix. The error was: Trying to find appointment Outlook TimeCard 3 Personal Settings.
The operation failed. An object could not be found.
|
| 27 August |
Several bugfixes:
"Saving all the comboboxes into BillingInformation"
A runtime error message with error number #438 might occur when you get new meeting request.
"Attempting to determine if the current item is properly filled out"
"Reacting to sheetchange"
|
| 22 August |
TimeCard Single Personal Setting dialog has been
redesigned to fit within 800X600 pixels resolution.
The bug that sometimes made Vista ask for new Scripting Dictionary object is fixed
also for the Single version. |
| 6 August |
Critical bug fix for the
workgroup version: On some Vista machines, TimeCard
users got an error report about Scripting.Dictionary object.
This is fixed in the TCAddin.dll version 4.2.0.159 onwards |
| 28 July |
Office Web Component fix: The problem occurred when
OWC was corrupt. TimeCard first checked for OWC 10, then OWC 9 and then OWC 11. If the user had a corrupt OWC 10, we recommend them to upgrade to OWC 11, but the check our app did
was till OWC 10, and once the app found it, it assumed OWC 10 was working. Then came the error message:
"Component 'OWC10.DLL' or one of its dependencies not correctly registered: a file is missing or invalid
#339 "
Now the sequence of checking for OWC starts with OWC 11, then 10 and then 9. |
| 9 July |
Two changes of TimeCard workgrop version:
-
When using the reporting via ASP option in a client, the reportPath.txt file available under 'My Documents\My TimeCards' is deleted. This reportpath.txt stores the TimeCard workgroup folder (shared folder), and is not required in ASP reporting option.
-
The trial period is now extended to 30 days
|
| 23 June |
Addition of two fields in the Display option of
TimeCard Reporting Tool: Partially marked & Both
marked and Partially marked appointment. |
| 19 June |
Version 4.2 of TimeCard single user version is
published, with the same new features as in the
workgroup version (see below) except the language
choice.
Small update of the workgroup version. Now reporting
of appointments with all fields empty is allowed.
These fields can then be filled with default values.
Also fix of a bug that prevented certain customers
from upgrading and of the bug that a cube was not created if meta field had more than 24 characters or special characters. |
| 13 June |
Version 4.2 of TimeCard workgroup version is published. It has several new features:
- Language options: each user can select the language of the operating system or another of the supported languages.
- Default value for empty fields: once the administrator has enable this option, if a user reports an empty field it will automatically take the data set default by the administrator.
- A location field in tblReports. When a user reports time, the location field will be transferred as well.
- Start-time is added in tblReports: when the user reports an appointment, the time of the appointment is also reported
- A new table included, tblPlanning (identical to tblReports). When a user reports time
‒ all entries for this person are deleted from the tblPlanning
‒ the user’s calendar entries from the latest post and for the next 12 months are posted in the tblPlanning. Same rules and settings apply as in a normal reporting.
|
| 21 Mars 2008 |
The TimeCard Reporting dialog depends on the availability of an
ActiveX control (mscomct2.ocx) to use the Date Picker control. If it is not found in the client system, the functionality is sufficed with three drop downs for Day, month and year. To avoid this, the
ActiveX control is now installed with the setup if
not available in the client machine. |
| 19 November |
TimeCard for Outlook Worgroup edition now has an
updated .sql file which corrects two errors connected
with using TimeCard with an SQL Server. |
| 26 October |
Most corporate networks include some kind of security
infrastructure that is intended to block certain types
of communications. Customers who connect to the Internet
from behind a corporate firewall, or via a corporate
proxy server, may have difficulty with product activation
as a result of these security measures. To overcome
this restriction, the application will automatically
launch a wizard for manually activating the license
key via a standard web browser. |
| 29 September |
Small bugfix of registration, TimeCard Single User |
| 27 September |
Windows common control 6 (mscomctl.ocx) is now included
in TimeCard Single User installer.
Changes in the registration form:
The registration form is visible all through the registration
process. A new progress bar is introduced that shows
the activity during this period, along with label that
informs the user that the application is trying to contact
the server. Earlier the registration form was hidden
until registration either succeeded or failed. This
led to insecurity about the process, especially if the
connection was slow and it took time to contact the
eSellerate server for authentication of the license
key.
When the TimeCard administrator registers the TimeCard
workgroup version, the key is now saved to the database
so that it is accessible for other users of the workgroup.
In the previous version, when the personal setting tool
was run by an unregistered user, it detected the key
from the database and tried to register in the background.
This resulted in a delay with no status report on the
process. Now the key is loaded/authenticated via the
registration box showing the registration progress.
Bug fixes:
In the past versions, when registering a TimeCard additional
license, the personal settings tool sometimes still
asked for a license. This has been fixed.
In previous version of TimeCard, when the option 'Write
TimeCard data in subject' was selected, there were inconsistencies
in the way the data was written in the subject. With
Outlook 2007, the data was not written at all.
The following have been refined/added when writing TimeCard
data to subject:
- TimeCard keeps track of the subject field, and
if it contains a TimeCard data, any changes in the
meta data are reflected to the subject as well.
- When editing an existing appointment, if the
subject line does not contain any TimeCard data
(but is not empty), then no data is written to the
subject. When the subject line is empty, the data
are written to the subject.
- Earlier TimeCard data written in the subject
field could start with a comma (,) - which is a
wrong format (not fatal though). This is fixed now.
- The TimeCard data are reflected to the subject
of the selected appointment even from the main calendar
explorer.
|
|
See older revision history
|
