Home >Products >TimeCard >Revisions       kalmstrom.com site map icon Site map  

TimeCard – latest revision history and current file versions

Current file versions

Filename Version Last changed
Common Files:
TCReporting.exe 4.4.0.16 2012-05-14
TCAddin.dll 4.4.0.63 2012-05-14
TCCube.exe 4.4.0.2 2012-01-27
OLAPReporting.exe 3.01.0319 2010-06-21
eSellerateControl365.dll 3.6.5 2009-06-01
Safekalmstrom.dll 4.8.0.1184 2010-06-21
Workgroup files:
TimeCardWorkGroupSetup.exe 4.4.11 2012-05-14
TimeCardClientSetup.exe 4.4.0.5 2012-01-27
TCCommonSettings.exe 4.4.0.17 2012-05-14
TCPersonalSettings.exe 4.4.0.41 2012-05-14
TCToolbar.exe 4.2.0.89 2009-06-01

TCHomePage.htm

2007-04-16
TCReport.asp 2008-07-09
TCPlanning.asp   2008-07-09
TCCT.exe 4.4.8 2012-02-29
CreateDBTC.sql   2008-11-27
version.xml 23 February 2010, 12:57:56
Single User files:    
TimeCardSingleSetup.exe 4.4.9 2012-05-14
TCPersonalSettingsSingle.exe 4.4.0.9 2012-05-14

TimeCard icon
Latest revision history

14 May New feature added “Add metadata in appointment body”. When this feature is enabled TimeCard automatically adds TimeCard data in meeting requests when the invitation is accepted.
29 February A bug when users opened a meeting request in a new window is solved in this minor update
28 January Version 4.4

Enhancements:
  • New feature in the Workgroup version: Report on behalf of.
  • TimeCard does no longer give an error message when Outlook reacts slowly, and Outlook does not have to be restarted.
  • TimeCard is now compatible with the not yet released iCalendarTimeCard for iOS devices.
Bug fixes:
  • The appointments metadata on the To-do bar was not refreshing properly.
  • Some users were not able to open TimeCard Personal Settings, TimeCard Reporting and TimeCard Statistics when the option “Resize drop-down fields to available space” was enabled.
  • If “Enable E-mail/Domain settings” was enabled and if the user first opened the Emails tab and then the Person tab, when the user selected the Person list it started to give popups of the metadata list.
  • The old brand name kalmstrom.com Outlook solutions in the TimeCard client tool was changed into kalmstrom.com Business Solutions.
  • The Personal Settings of the Single version is dependent on the file comdlg32. It is normally present on PCs as it is a Microsoft redistributable component, but if it was not TimeCard gave an error. Now this ocx file is added to the setup.
  • If the TimeCard Enable email/domain setting was checked the TCCOmmonSettings.exe did not preserve the Admin specified option. At each exe start it showed the option checked.
2012  
8 September Minor update to fix a bug when you used TimeCard with Office 2010: the metadata values in the dropdowns did not refresh when the user first selected a marked appointment and then a blank appointment.
9 August TimeCard Single optimized for Office 2010 32-bit.
When keywords like department, person, subject, month, weekday, date, date - week , appointments, hours, rate or category were used in metadata or expenses captions the user had a run time error at time of cube creation, because these keywords are already used in the cube. Now they will instead get a message explaining that these words cannot be used.
5 August TimeCard Workgroup optimized for Office 2010 32-bit.

The Email/Domain Mapping Feature was added to the workgroup version also, refer to entries of 22 and 24 June.

Bux fixes:

If there was a change in the database structure (like we added one more table tblEmails in this version) TCPersonalSettings.exe was not able to upgrade the SQL database structure while TCCommonSettings.exe was able to do this. Now TCPersonalSettings.exe is able to upgrade SQL database structure also. There were no problems with Access.

When keywords like department, person, subject, month, weekday, date, date - week , appointments, hours, rate or category were used in metadata or expenses captions the user had a run time error at time of cube creation, because these keywords are already used in the cube. Now they will instead get a message explaining that these words cannot be used.
3 July Bug fixes in TimeCard Single:
Due to a corrupt reference, TCReporting.exe was always asking for install of OWC, even though it was already installed.
Some phrases were shortened and labels lengthened in the Personal Settings dialog, to avoid text in two rows.
24 June Now TimeCard Single can also set default metadata from the Email/Domain list if the email is dragged from one Outlook email window into other Calender window.
22 June Update of the Single version due to change of digital signature.

New feature added: Map E-mail ID or Domain to TimeCard properties. Useful if you drag e-mails to the Outlook calendar to make appointments from them.
21 June Update of the Workgroup version due to change of digital signature.
31 May Update of the Workgroup version.
  • The ”Mark new appointments with default metadata” option is added to this version also (refer to update of Single version 3 May).
  • The “Write Time Card data in subject” feature is changed. Earlier TimeCard data was not added to the subject if a subject was already present. Now TimeCard will write metadata in the subject also when it already has text and separate subject and metadata with ::. It will look like this: “metadata1, (metadata2), (metadata3)::Subject”
  • The Common Settings dialog did no longer fit in a 800x600 screen. This is now fixed.
4 May A bug in yesterday‘s version made the default values spill over on e-mails. This is now fixed.
3 May The Single version was updated with the applicable features from the latest Workgroup release. Also, a new option was added in Personal Settings, ”Mark new appointments with default metadata”. When selected the new appointments will have the default metadata visible in the appointment, not only reported to the database.
16 April Enhancements and bug fixes:
  • If metadata contained a space at end, it was not possible to set appointment metadata properties in Outlook. It also gave a run time error in TCCommonSettings.exe. This error came came when data was entered directly into the database not by TCCommonSettings.
  • Earlier TimeCard Workgroup inserted all appointment records into the database and then updated its status into TCReporting and Outlook. If the connection was lost in between, the appointments status was changed in TCReporting and Outlook, which lead to double posting of appointments into the database. Now TCReporting will update appointment POST status in the list and also in Outlook after each database entry.
  • A run time error was coming when users installed TimeCard and opened an appointment into a new window without saving Personal Settings first time, or when Personal Settings did not have any metadata selected.
27 February Update of the Single version with the two new features added to the Workgroup version 24 Feb. see below
24 February Update of the Workgroup version

New features:
  • Added the possibility to export appointment body into the Excel sheet, when reporting. A check option 'Include appointment body into Excel' is available in the TimeCard Personal Settings dialog, which can be used to toggle the inclusion of this field. By default, it is unchecked.
  • For TimeCard metadata lists of more than 1000 items, a new button (i.e., 'more...') will become visible just adjacent to the Metadata combo drop down control on the ribbon (for Outlook 2007 or above only). Clicking this 'More...' button opens a dialog box where it lists all the available items of the metadata list (>1000) and the user can select one of it. This is implemented as a workaround to the limitation of 1000 items in the drop down control in Office Ribbon.
Bug fixes:
  • If the auto-add option of TimeCard properties to the client system is enabled in TimeCard Common Settings, changes (eg. add/remove/edit) of metadata values in Common Settings were not reflected in the client system even if the client Outlook was restarted. It was only updated if the user ran TimeCard Personal Settings or if Outlook was restarted twice. This is now fixed.
  • Also, newly added items that were added by auto-update were not sorted alphabetically on first opening. Now the items in the drop downs are sorted from the beginning.
15 January TimeCard Single is updated with the applicable enhancements from the Workgroup version release of 12 January.
12 January This update of the workgroup version has full support for Unicode and also includes the new updated OLAP Reporting Tool with full Unicode support. For this the file comctl32.ocx is needed. Most users have it installed, since it is a general ActiveX component for Windows. If this component is corrupt or removed, TimeCard will detect it and give the user an option to download it from a Microsoft site.

Some non critical bugs were also fixed:
  • Sorting issue in TCPersonal Settings when reporting was set to an ASP page.
  • If 3 meta data were used, and if the option "Write TimeCard data in subject" was enabled in TimeCard Personal Settings, only the first chosen value was written in subject of the appointment.
  • Wrong encoding in the category/super category tree in TimeCard Common Settings as well as in the default value for empty field, Count Cost etc. resulted in containing a string like "????????" instead of the actual (Unicode) characters.
  • For the metadata by which costs were counted, the tree in Common Settings showed only one level. This error happened when the Metadata list contained category, but not super category and the data was pasted from an Excel file. If the user input directly on the spreadsheet, there was no error.
2010  
24 November Upgrade of the Single version, so that it corresponds with the Workgroup version in applicable parts. These changes are also made:
In TimeCard Personal Settings it is now possible to enter a value longer than 255 characters as one of the metadata.
The TimeCard toolbar dropdowns in Outlook are adjusted to work within 800x600.
The TimeCard Personal Settings is also adjusted to show up under a 800x600 resolution.
17 November Upgrade of the Workgroup version.
Changes and enhancements:
The trial period is increased to 60 days, to give companies with many user more time to evaluate TimeCard..
The Buy button is removed from the Register dialog, as per the changes in our licensing scheme to a Community model with monthly subscription.
In the Common Settings dialog the expenses-button was too far away from the checkbox and caption. Now it is fixed by placing them next to each other.
Bug fixes:
In the Reporting dialog, double clicking on a posted cell would result in the first column being out of sight.
For users with three TimeCard values, the third dropdown box in the TimeCard toolbar in the Outlook Calendar folder was be active all the time, even if no appointment item was selected.
Once the TimeCard Client tool was installed, trying to run the TimeCard Personal Settings might result in the following message: "Unable to connect to current Outlook folder!".
When setting the 'Count Cost by' to "Person" and then checking the 'Admin specified' option, you will get another meta data tab named "Person". If you had three other metadata and clicked the "Person" tab, you might get a run time error.
These bugs are now fixed.
Also error messages about "SQL Server does not exist or access denied" and "The remote server machine does not exist or is unavailable" are fixed in this new release.
12 October Improvements and bug fixes:
  • In Outlook 2007, users with Greek or Hebrew or Russian languages in OS, might not be able to add/edit anything in the appointment fields and the whole screen (inspector window) might appear locked or frozen. This was due to certain bugs in the 3rd party Outlook redemption library that we make use of in TimeCard. As
  • TimeCard now supports non-Latin characters such as Hebrew or Greek in the metadata lists, TimeCard Personal Settings is also updated to support Unicode, in the listbox (where the user can select their metadata lists).

  • The TimeCard addin is modified to add support for Office 2007 ribbon. Now when you open an appointment, instead of having the TimeCard drop down fields in the right pane, you will find them under the Ribbon portion.

  • Overflow in TimeCard Reporting tool - Under Personal Settings, if the 24h Events option is uncheck and the option "Convert whole day events to hours" is enabled, an overflow error comes up when reporting if the entered number is greater than 24 (24 hrs).
    Solution: In TimeCard Personal Settings, the maximum value one can enter in the 'Convert whole day events to hours' is restricted to 24. Also, the maximum value one can enter in the 'Remove lunch time from appointments than 7 hours' is 7.
Only for the Workgroup version:
  •  If you have upgraded to the previous TimeCard (workgroup, one with TCPersonalSettings.exe - version 4.3.0.303), the personal TimeCard settings might be saved under a different registry location (having a long Chinese characters).This is now fixed.

  •  Warning message remained after database was selected in TimeCard Personal Settings tool. When running TimeCard Personal Settings and if the reporting path was invalid or not set, a message appeared asking the user to specify the path to the TimeCard Workgroup database. But even after selecting the correct TimeCardConnection.txt file, the message box remained. 
30 September Some bugs in the Workgroup version were fixed:
  • Fixed error due to corrupt OWC11 in project file.
  • In the TimeCard Reporting tool, clicking on one of the rows, and then scrolling down resulted in the dropdowns staying on the original position while the grid was scrolled.
  • If the TimeCard Reporting tool had a long list of rows (longer than the dialog's height), scrolling down till the end resulted in the hiding the last row partially.
  • Fixed the error in OLAP Reporting Tool that came when a user did not have permission to create the license file under the Program files folder. This typically happened on Vista and Win7. Now TimeCard will create the license file 'olap.license' under 'My Documents, in a 'My Olap' folder.
25 September TimeCard Workgroup is now made compatible with Unicode characters such as Greek/Hebrew. Also two minor bugfixes.
28 August Bug fixes and enhancements:
  • If you updated to the last version of TimeCard Workgroup, you might get an error when running TimeCard Reporting tool (TCReporting.exe): "Component 'OWC11.DLL' or one of its dependencies not correctly registered: a file is missing or invalid" This was due to corruption in the project build process (and only in the TimeCard Reporting tool), and is now fixed.
  • The personal settings dialog now appears in minimized mode when starting up.
  • Background color of some controls in Personal Settings did not blend exactly with the form.
  • The super meta-categories tree in Common Settings should only be shown for TimeCard values that has category and super category. But if you chose to have metadata for Customer but not for Task, the tree was still shown when you selected the tasks.
  • The controls in the license dialog form did not fit in properly.
  • In certain language such as Swedish, certain phrases did not fit the control.
19 August TimeCard can now report up to 500 appointments at a time.
Bug fix: When running statistics from the TimeCard toolbar, some users that had all 3 meta fields enabled got the following error message: "There is no data in the database ... Statistics will not work, yet!"
12 August Some bug fixes in the workgroup version:
1) When users accepted a meeting request and if the "Metada datafield required" was enabled, users were warned with a message that all required metadata were not filled out.
2) Overflow problem was fixed
3) When installing TCWG client tool setup on a system, the TimeCard toolbar was not visible (available) for other users, except for the particular user who had installed it. This only happened for new installations of version 4.3, not for upgrades.
4) When using the SQL server database, and if the user did not have permission over the database or if the SQL server or the TCWG network path was invalid, TC personal settings prompted the user to browse for the path to the TimeCard3.mdb or TimeCardConnection.txt. Even if the user selects the correct TimeCardConnnection.txt (from the TCWG network folder), he was still prompted to select an appropriate file. This is fixed now
1 August A bug fix in both versions: when reporting, if you run the 'Export to Excel' button, you might get a runtime error with "Type mismatch #13" . This happened if TimeCard failed to get  the reference to the correct Excel version, but now this is handled in a better way.
31 July By mistake the Single trial period was set to 15 days in yesterday's release. Now it is back to 30 again.
30 July The Single User version of TimeCard has been upgraded to V 4.3 with the applicable new features from version 4.3 of TimeCard Workgroup:
  • New expense fields (5 in numbers) available in Calendar appointment. The titles for the fields are customizable to suit your line of requirements. These can be activated from the Personal Settings. Once activated, the user will see a new additional button 'Expense' in the TimeCard toolbar. Click this button, will popup a form to enter the expense related data. These fields are available for reporting to the database, as well as in the cube (for statistics).
  • Now, you can use TimeCard with any calendar, other than the default (including shared ones or secondary mailbox calendar). The TimeCard toolbar will be visible to all calendars. To report appointments of the particular calendar, just run the reporting dialog. Note: To be able to report appointments from a shared or secondary mailbox calendar, the user needs to have editor or higher permission on that calendar, otherwise, reporting will fail.
  • Mandatory Metadata fields - A new option 'Make all TimeCard meta fields mandatory' is now available in the Personal Settings. With this settings, the user is restricted from leaving any meta fields empty when tagging appointments. If the user does not fill all the mandatory field, TimeCard addin will prompt the user if to try again or discard the changes to the appointment. Exception: Appointments marked 'private' are however exempted from this mandatory check.
  • With version 4.3, TimeCard uses redemption Outlook library to bypass certain Outlook security restrictions (which otherwise are not possible using the object model of Outlook). Now, TimeCard can report the note field (body) of an appointment at any length (full body content). (SafeKalmstrom.dll is now installed to the TimeCard for Outlook program files folder)
  • Excel report export - When user clicks the excel button in the Office web component (OWC) grid, an excel report is prepared for all the appointment listed under the TimeCard Reporting grid. This excel report is saved as Report.xlss under 'My Documents\My TimeCard' subfolder.
2 July New Feature: New expense button available in the Calendar appointment. The titles for the fields are customizable to suit your line of requirements in TimeCard Common Settings, where this feature is activated. If activated, each user (client) will see a new additional button 'Expense' in the TimeCard toolbar. Click this button, and a dialog to enter the expense related data will be shown. These fields are available for reporting to the database, as well as in the cube (for statistics).

The number of rows in the Excel grid in TimeCard Common Settings is extended to accommodate 10,000 rows.

Fixed bug in the Export to Excel feature: on some systems the report was saved into .xlsx format though they did not have Excel 2007 installed.
9 June At upgrade to the workgroup files of TimeCard 4.3, the Client tool setup (TCCT.exe)was not always updated. This is now fixed.
1 June Version 4.3 with many new features:

  • Now, you can use TimeCard with any calendar (including shared ones or secondary mailbox calendar), not only the default one. The TimeCard toolbar will be visible to all calendars. To report appointments of the particular calendar, just run the reporting dialog. Note: a) To be able to report appointments from a shared or secondary mailbox calendar, the user needs to have editor or higher permission on that calendar, otherwise, reporting will fail. b) To be able to report appointments which are already tagged with TimeCard metadata in a shared calendar, the user needs to have the same selection of the metadata lists as that of the mailbox's owner (calendar owner).
  • Auto update of the TimeCard Client Tool - When the administrator has upgraded the workgroup files in the network share to the new TimeCard, the existing TimeCard client addin in Outlook would automatically check and compare the version and if a newer version is available, it would automatically run the client tool setup to perform the upgrade, after prompting the user. (version.xml file is introduced in the TCWG network shared folder with version 4.3 of Timecard)
  • Silent Installation - If the existing TimeCard addin detects a newer version (from the TCWG workgroup folder) it will be run in silent mode, that is, there will not be any dialog forms. However, it is recommended to shutdown Outlook, once you have clicked 'Yes' to the auto-update confirmation message. (Silent installation works by passing the TimeCardClientTool.iss, which is available under 'My Documents\My TimeCard' folder. Note: silent installation will work from version (both minor or major updates) available after 4.3)
  • Mandatory Metadata fields - A new option 'Make all TimeCard meta fields mandatory' is now available in TimeCard Common Settings, with which the TimeCard administrator can restrict users from leaving any meta fields empty when tagging appointments. If the user does not fill all the mandatory field, the TimeCard addin will prompt the user if to try again or discard the changes to the appointment. Exception: Appointments marked 'private' are however exempted from this mandatory check.
  • With version 4.3, TimeCard uses redemption Outlook library to bypass certain Outlook security restrictions (which otherwise are not possible using the object model of Outlook). Now, TimeCard can report the note field (body) of an appointment at any length (full body content). (SafeKalmstrom.dll is now installed to the TimeCard client tool program files folder)
  • Hiding Report button - the TimeCard admin can also set a local registry value in each user’s system, such that it can be used to enabled/disabled the reporting button in the TimeCard Outlook toolbar. This scenario would be important particularly, if the organization already has an in-housed tool that process the timecard appointment of the users directly from the Exchange Server. To use this feature, just add a new key HKEY_CURRENT_USER\Software\Kalmstrom.nu\TimeCard\Settings\HideReport and set its value to 0 or 1. (0 - show report and 1 - hide report button)
  • Excel report export - When a user clicks the excel button in the Office web component (OWC) grid, an Excel report is prepared for all the appointment listed under the TimeCard Reporting grid. This excel report is saved as Report.xlss under 'My Documents\My TimeCard' subfolder.

Changes to installers:
1) The installers are now updated with the latest graphics (horizontal banner and welcome dialog) in both client and workgroup setup.exe
2) The custom dialog in the client tool setup of enabling user to choose between add-in DLL and HTML folder homepage option is now removed, and the add-in DLL option will be installed.
3) Version changes from 4.2 to 4.3 in both installers
6 March Upgrade of the Single User version. The manual upgrade option in TimeCard Single User installer was only meant for upgrading from version 3 to 4. Therefore, when a user specified an existing TimeCard folder to upgrade, the installer said that the selected folder was an invalid folder. This only happened when the user tried to upgrade manually to TimeCard version 4 or above. Now the TimeCard installer allows manual upgrade of version 4 to a later version (eg. 4.1, 4.2 etc) by specifying an existing TimeCard folder.
The new version also has the new OLAP Reporting Tool included, and the company information is updated to kalmstrom.com Business Solutions.
2009  
18 December Improvement of the workgroup version makes it easier to use TimeCard in a system with locked machines.
Earlier the TimeCard add-in (TCAddin.dll) was registered under HKEY_CURRENT_USER registry hive, which meant that it was only registered for the current user (the one who performed the installation) even if the files were installed for all users on that system.
Now the add-in is registered under HKEY_LOCAL_MACHINE, which means that anyone in the administrator group can install the product for all users of the machine.
6 December Minor bug fixes to the workgroup version
27 November New features:

  • TimeCard properties added in the Common Settings can now be set to be added automatically to the client system. This way, the client does not have to run the Personal Settings manually to select those new additions (tags) from the workgroup database. This option can be enabled/disabled in the TimeCard Common Settings dialog ("Enable Auto-add of TimeCard properties").
  • The Statistics button in the client users can now be disabled (made invisible). This is possible only when the admin has selected Person as cost-carrier and the rate is specified by admin. Doing so, a new option 'Hide Statistics' will be available. Checking it will populate the choice to the Personal Settings automatically. (The users don't have to run the Personal Settings manually, as checking will be performed automatically during startup). 

Fixes of two temporary errors from the last update, both versions:

‒ Copies of reported appointments are now available for reporting again. Earlier, they were shown as reported in the TimeCard Reporting tool, due to which, copies could not be reported.

‒ In a new installation, the last update of TimeCard only showed one default meta list ("Customer"). In this release, two default meta lists are show by default ("Customer" and "Task"), as it was before and as it is described in the documentation.

The SQL file 'CreateDBTC.sql' is updated to add additional fields in tblPersons table.
20 November Two more bug fixes:
‒ When tagging categories field of appointment from outside of TimeCard (that is, via Outlook), the values in the meta field drop downs in the addin might not show up.
 ‒ Two meta fields in TimeCard can not have the same value in the list. To prevent this from occurring in the first place, the user/admin will be prompted to change the meta lists in the Common settings (for TCWG) or Personal Settings Single (TCSU) if any such duplication occurs in two or three meta field lists.
19 November Some bugfixes:
‒ Bug in reporting when using a single TimeCard property
‒ If the user specified an erroneous parameter in the Personal Settings (like wrong value in the database connectivity), TimeCard did not allow the user a second chance to to amend/correct the anomaly.
‒ When a user tried to report and the database connection was offline/unavailable, an unfriendly error message was shown. Now TimeCard shows a friendly message about the unavailiability of the database and exits.
An upgraded OLAP Reporting Tool was also added.
24 October
  • New option in the TimeCard personal settings 'Resize drop down fields to available space'. Checking this option will allow the TimeCard addin to use the maximum available space in Outlook, thereby increasing the width of the drop down fields to accommodate lengthy values.
  • Fixed the the progress animation visibility in TimeCard reporting even when the reporting has finished.
  • Tooltip now enabled when mouse hovers around the drop down fields (so that selected value that is longer than the drop down is shown as tooltip for better recognition)
  • The checkbox 'Admin specified' in TimeCard common settings, now enlarged to accommodate all language phrases.
23 October The Workgroup version updated to fix a bug in yesterday's release.
22 October New feature in the workgroup version allows admin to specify personal rates of all the TimeCard users in TimeCard Common Settings. If the person is selected as the cost carrier, there are now two ways of specifying rates in Common Settings:
  1. By the admin ‒ there is a checkbox "Admin specified" just below the cost carrier drop down. Checking this checkbox will allow the admin to define the hourly rate of each TimeCard user, and the users will not have the option to define their own rates in their personal settings. A new tab ("Persons") is loaded/unloaded as soon as the checkbox is selected/unselected. Only the category and rates fields are editable. No person can be added as well.
  2. By the person ‒ the same as it used to be, each user specifies her/his rate in the Personal Settings. 
In Personal Settings, the personal rate option would not be visible when the "admin specified" is enabled

A new activity progress animation is added to the TimeCard reporting tool.

Bug fix: When there were identical values in two or three meta lists and a user tagged an appointment with anyone of this identical values in any drop down, then same value was assigned to other dropdowns having the same identical value in their list. This is fixed now!
6 October Various bux fixes: registry problem, error when several meta dropdowns had the same value, "please start Outlook manually".
4 September Minor bug fix. The error was: Trying to find appointment Outlook TimeCard 3 Personal Settings. The operation failed. An object could not be found.
27 August Several bug fixes:
"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 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.


Questions? Ask us!



or send us an e-mail




Don't have the latest version? Download

– the workgroup version

– the single user version

Upgrades are free for Community Members
and Single Support customers.




Always the latest news
about TimeCard in
the kalmstrom.com blog



 Follow kalmstrom.com on
LinkedIn Facebook,
Google+  or Twitter!






OLAP Reporting Tool iconFacilitate business intelligence by following up performance with the statistics tool
OLAP Reporting Tool
–– integrated in TimeCard.



TimeCard
is updated often. The main reasons  for this are:
  • We want to adapt to and take advantage of changes in the Microsoft software we build on.
  • When we receive reports about bugs we fix them as soon as possible.
  • Of course we also try to add new features that our customers ask for.
 
Products Community Requirements Services iOS Tips Contact About Us Blog
   Security and integrity
Copyright  Kalmstrom Enterprises AB  All rights reserved