Version 29 goes live 1 July 2006

Known issues


This page details any known issues with the Version 29 release.

As issues arise that affect clients, they will be noted here, along with suggested workarounds or links to update patches.

This page will be updated within an hour of any known issue occurring.

Unresolved issues have a red heading. Resolved issues have a black heading.

If you are notifying us of a new issue please send details to support@talman.com.au.
Please always send correspondence to this email address including replies and follow up.

 Cash Account Sales issue - Issue Resolved
Cash Account Sales crashes - Issue Resolved
Posted: 2:32pm Wednesday 19 July 2006

When using the Cash Account Sales program, if you attempt to add a new Purchase Account from the 'Add purchase account' button the program will crash.

There is no workaround within the program. The only way to avoid the crash is to create the purchase account before using Cash Account Sales program.

This has been fixed in 6F release available on 25 July 2006.

 Averaging + Allocation issue - Issue Resolved
Averaging and Allocation program issue - Issue Resolved
Posted: 11:53 am Friday 14 July 2006

Some clients have experienced an issue with the Averaging and Allocation program when deallocating lots and allocating new lots at the same time.

If an order is chosen, lots allocated to it (from the Add lots page), existing lots in the order unticked, and then the Allocate button used to finished the allocation, the following may occur:
- deallocated lots will be restored to previous sales account
- newly added lots are ignored and not allocated to the order

To work around this you need to perform deallocation in a separate step to the allocations eg
- deallocate lots by unticking them on the order, and click the Allocate button to finalise this deallocation
- then add lots to the order, tick them and click the Allocate button to finalise this allocation

This issue has been fixed in the 6F release available on 25 July 2006.

 Import from DBF error - Issue resolved
Import from DBF error - Issue resolved
Posted: 11:14am 07 July 2006

A few clients were experiencing an error when using the Import from DBF program. This is only in certain Terminal Server and Citrix environments.

The program has been fixed to accomodate these environments and is being manually released to each of these clients (3 clients in total).

It will be made part of a general maintenance patch on 14 July 2006, however if you are experiencing this issue please contact support@talman.com.au and the program will be made available to you immediately.

 Printing issues - Advice
Printing issues - General advice
Posted: 4:15pm 03 July 2006
Updated: 12:14pm 05 July 2006

A small number of clients have started experiencing issues with printing reports. Usually the result is some reports being cutoff when printed.

If this happens please check your printer settings - you may your paper type set to Letter - this needs to be set to be A4.

Previously our printing routines used to override the printer settings and forcing the paper to A4. The latest release has been enhanced to honour the printer settings (this is a more flexible approach for our clients). As a result some cilents have had issues where their current printer settings are set to Letter, and are now having parts of the reports cut off (or cropped). This issue is fixed by simply changing your printer settings to be set for paper size of A4.

Note, changing your printer settings may not persist in all cases. There is a known issue with Terminal Server environments. In this case you need to stay logged in for atleast 60 seconds before logging out. See the following Microsoft Knowledge Base article for further information:

http://support.microsoft.com/?kbid=243942

 Invalid path or filename - Issue resolved
Invalid path or filename - Fix is in testing
Posted: 6:05pm Thursday 29 June 2006
Updated: 4:23pm Thursday 06 July 2006

A few clients have experienced this error when running the Import from DBF program. The program will give an error stating theat a temporary file cannot be found. The error does not occur everytime, and by clicking Ignore the ure can usually continue on and perform the import.

The issue has been identified and a fix is currently being tested.

This issue has been identified on a single client site and is specific to their environment. As such it will be fixed manually on that site. It will become part of a non-urgent maintenance patch to be released on 14 July 2006.

 Procedure file 'n:\vfox\wp\wpvalid.app' is not found - Resolved in Patch 2006.5.6d
ERROR: Procedure file 'n:\vfox\wp\wpvalid.app' is not found - Resolved
Posted: 4:59pm 28 June 2006

We have discovered this issue on a few select client sites. It is related to the latest release and occurs when exiting the system.

This has been fixed and is part of patch 2006.5.6d available 30 June 2006.

 Autocomplete not found error - Resolved 27 June 2006
ERROR: Property AUTOCOMPLETE is not found - Resolved
Posted: 12:29pm Tuesday 27 June 2006

This error occurs for a few clients on the Process Wool Delivery Orders program v9.00 and below.

This is due to a refresh issue that is not setting some properties correctly.

The fix has been applied to select sites that were experiencing the issue.
It will be made part of a general release available on the afternoon of 29 June 2006.

 The specified file or path was not found - Work around
The specified file or path was not found - Work around
Posted: 8:39pm 23 June 2006

Some WoolBuyer clients are experiencing this error 'Specified file or path was not found' when going into the WoolBuyer system, using the new menus.

This is due to a missing bitmap file.

To fix simply download this bitmap file and put it into your n:\vfox\bmp\16\ folder.

This will be fixed in the next patch.

 Grid row highlighting 'feature' - Resolved in Patch 2006.5.6c
Grid row highlighting - Difficult to view on some connections
Posted: 6:28pm 23 June 2006

The new release includes a feature which highlights the currently selected row in a grid.
Some users have experienced display problems with the highlighting, with blotchy, grainy highlighting.
This has usually been experienced on Terminal Server conntections.

This can sometimes be improved by increasing the colours displayed. If possible try to display atleast 256 colours.

This can be done by setting the Display properties on your connection:
On the Desktop, Right click and Select Properties
Choose the Settings tab
Set the Colour quality to the highest number of colours.
Click Apply and then OK.

If you are unsing a Terminal server login, you will need to change the number of colours on your Terminal Server connection:
Find the Talman icon and right click
Select Edit
Select the Display tab and make site the Colours setting is set to the highest possible
Go back the General tab and click Save As and then click Yes to overwrite your existing file.

Now try connecting in to test the changes.

This feature has now been disabled by default in Patch 2006.5.6c released 4:39pm 26 June 2006.

 Derivatives will not save - Resolved in Patch 2006.5.6b
Derivatives will not save - Resolved
Posted: 3:27pm 23 June 2006

Some clients may experience an error when trying to save derivatives. This is due to an index on the derivatives table not being correct.

This has been fixed in Patch 2006-5-6b.

 Delivery orders LOCAL/OVERSEAS change - Work around available
Delivery orders LOCAL/OVERSEAS order combo refresh - Workaround available
Posted: 12:15pm 23 June 2006

WoolBuyer users may experience a refresh issue on the Delivery Orders program. On the Delivery Details page you can change the Order type combo between LOCAL and OVERSEAS. Changing this entry will usually change the format of the Final Destination combo.

However an issue with refresh means that this combo does not update.

This is currently being resolved.

A work around exists:
Click on the Order type dropdown.
Change to the type you require.
Use the mouse to move out of the dropdown by clicking into the Pack type dropdown.
Click back into the Order type dropdown and press Enter to move out of it again.
This second time the Final Destination will refresh.

 Input Cash Receipts - Resolved in Patch 2006.5.6b
Input Cash Receipts displays paid lots - Resolved
Posted: 11:21am 23 June 2006
1. The Input Cash receipts program will list already paid lots on the List page. This is incorrect and causing confusing to users.

2. The program allows update of payment details of flagged lots if the invoice amount and cash received do not match - except for the last lot.

3. Does not update payment details on the last lot.

This has been fixed as part of patch 2006.5.6b available from 23 June 2006.

 ERROR: Missing comma - Resolved in Patch 206.5.6b
Error: Missing comma - Resolved
Posted: 10:47am 23 June 2006
Some clients are experiencing an error when printing Private Account Sales reports.

This is due to a syntax error in the report file being printed.

This has been fixed as part of patch 2006.5.6b available from 23 June 2006.

 ERROR: Class definition WP2LOTMANAGER is not found - Resolved in Patch 2006.5.6b
ERROR: Class definition WP2LOTMANAGER is not found - Resolved
Posted: 5:19pm Thursday 22 June 2006

After the upgrade, go into a system and run up Lot maintenance.
The program will crash with the error noted above.
This is due to the menu file in your system not being updated to the latest one (which will load the Class definition).

This has been fixed as part of patch 2006.5.6b available from 23 June 2006.

 Auto complete 'feature' - Work around available
Auto complete 'feature' - Resolved
Posted: 3:37pm Thursday 22 June 2006
Further updated: 10:39am Monday 26 June 2006

A behaviour change that has come with the Version 29 upgrade is the AutoComplete feature. This is by design and is enabled on many fields. It prompts the user with a dropdown of previously entered values on textboxes (similar to how Microsoft Outlook and many other Microsoft products work).

However, this functionality can be distacting in some cases (Eg when entering bales).

To turn it off simply use the following key combination: SHIFT + F12
This will ned to be done in each session.

To turn it off permanently you can adjust the following user table setting:
Table: DEFAULT
Code: AUTOCOMPLE
Text2: NO

At present the Text 2 field is set to YES. Simply change this to be NO

 Error when creating New Purchase organisation - Resolved 22 June 2006
Error when creating New Purchase organisation - Solution available 22 June 2006
Posted: 5:22pm Thursday 22 June 2006

Some systems will crash if attempting to create a New purchase organsiation.
This occurs with version 8.06b. It has been fixed in the latest version, which will be available in the updated patch to be made available shortly.

Resolved in updated Installer (2006_5_5e) made available 7:56pm 22 June 2006.

 ERROR: The fields in table xxx did not match database - Resolved 22 June 2006
ERROR: The fields in table xxx did not match the entries in the database
Solution available 23 June 2006
Posted: 5:24pm Thursday 22 June 2006

This is an issue on some systems that have an old mxwp.fxp file in their n:\vfox\wp\mx and n:\vfox\wp\dbfs\XX directories.

This will be resolved by a patch to be made available shortly.

Resolved in updated Installer (2006_5_5e) made available 7:56pm 22 June 2006.

 Strange n:\vfoxDI\ directory created - Resolved 22 June 2006
Strange n:\vfoxDI\ directory created - Solution made available 22 June 2006
Posted: 5:27pm Thursday 22 June 2006

On some systems a strange directory n:\vfoxDI\ has been created as part of the installer process.
The directory is not used and is not harmful in any way, but is confusing.
It can be deleted.

The updated installer will ensure this is not created.

Resolved in updated Installer (2006_5_5e) made available 7:56pm 22 June 2006.

 Online Catalogue - LH_SORG not found - Resolved 22 June 2006
Online Catalogue - LH_SORG not found - Resolved
Posted: 5:30pm Thursday 22 June 2006

Some ABS/TOPS systems may get this error when running Online Catalogue.
This occurs because the new versio of the program needs to have this field in the temporary table.
To fix, Select Transmission -> Transmission job.
In the transmission type, input WPCOL. Click List.
Delete the existing job.

The next time you start Online Catalogue a new job will be created. You will need to recopy data.
Note: no data is lost due to this.

Note: this is not a new issue, nor a v29 issue - you should be deleting the WPCOL job on a weekly basis. This should be part of your weekly maintenance routine.

Wool downloads
* requires Login