Jump to content


Ian Blew

Member Since 05 Oct 2000
Offline Last Active Aug 06 2007 08:06 AM
-----

Posts I've Made

In Topic: How are you doing on Version 6

26 January 2007 - 01:34 PM

We had to convert all our 'C' routines that were linked into the Kernel to use the new shared library method, but this was not much of an effort.



How did you do this? We're facing the same task so any A&G would be appreciated.

Cheers

PS: I'm not part of the development team that will need to do this, but need some answers so I can suggest solutions to them.

In Topic: 5.5 & Vista

26 January 2007 - 01:29 PM

PROIV won't be supporting Windows Vista until V6.1 (scheduled for release by mid-2007) due to having to change their development environment to a later release.

This is apparently because of major changes in Vista around the MFC libraries.

In Topic: error in opening print file

12 September 2006 - 10:41 AM

I presume you're running on a Windows Server.

Does the "PROIV Server" service login as a local administrator, or is it set to use the LocalService account?

We have 100+ Windows customers, many of whom have had the exact same error message (just printing thorugh our application, not specific to just Bus & Task) . It's due to the fact that when running as LocalService, PROIV doesn't always have access rights to create print files - it depends how the Windows Server is configured and whether file access is restricted.

In Topic: ProIV & SQL Server 2005

12 July 2006 - 02:36 PM

We have tried our application running PROIV 5.5 against a SQL 2K5 database on a Windows 2003 Server.

I'm not sure if it's our application architecture, but we have had problems with locking and deadlocks. It appears that SQL 2K5 has a new locking algorithm - a search for "SQL Server 2005 locking" on Google may provide some insights.

Please note that PROIV do not support SQL Server 2005 until PROIV v6.

In Topic: PROIV Client Build Number

17 February 2005 - 03:57 PM

InstallShield quote the following when explaining the use of version numbers for MSI distributions:-

"The version number must contain only numbers and must be in the format aaa.bbb.ccccc, where aaa represents the major version number, bbb the minor version number, and ccccc the build number. The value in aaa or bbb must be less than 255, and ccccc must be less than 65,535. You can include a fourth field, making the product version format aaa.bbb.ccccc.dddd, but Windows Installer does not use it.

The setup registers the major and minor version numbers as required by Windows logo guidelines, and the entire version string is displayed in the Add/Remove Programs panel. The version number is important because Windows Installer uses it in part to determine whether to apply an upgrade."


So who's correct??????
:p