We need to upgrade our porting set to support Oracle 10g. While we're at it I thought it would be good to upgrade our BW clients. Since we don't upgrade porint sets nor Baan clients very often I thought we'd get to the latest version of both, porting set 6.1c.07.11 and B40c.82 on the client. My question is:

Can I use an older client to access a newer porting set?
I'm having an issue with the 82 client - it seems when a user types in their name, it is capitalizing their letters in the user id. The user puts in us10556 and the error says:

2006-09-22[15:17:52]:E:US10556: ******* S T A R T of Error message *******
2006-09-22[15:17:52]:E:US10556: Log message called from /view/port.6.1c.06.07/vobs/tt/lib/ds_1/ds_bcnct.c: #181 keyword: DsSendNAck
2006-09-22[15:17:52]:E:US10556: Pid 21371 Uid 10556 Euid 10556 Gid 125 Egid 125
2006-09-22[15:17:52]:E:US10556: user_type S language 2 user_name US10556 tty ote locale ISO88591/NULL
2006-09-22[15:17:52]:E:US10556: Errno 0 bdb_errno 0
2006-09-22[15:17:52]:E:US10556: Log_mesg: Not authorized to run as user 'US10556'
2006-09-22[15:17:52]:E:US10556: ******* E N D of Error message *******

Baan says in their solution 13743 for the porting set that the porting set and BW are tied together:

"We advice to have always the latest BW version installed. But you can use a newer BW version against an older porting set version.
So it is not mandatory to update the portingset on the Baan server also, when installing the newest BW version on the client computers.
Although we advice to have also the latest version of the portingset installed on the Baan server.

The portingset and BW (bw.exe, bwprint.exe, etc) are always created as one build, and secondly the portingset components and BW components are separated from each other. So we end up with a "BW install" and a "portingset install".
This means that a certain combination of a BW version and a portingset version do have the same source code base.
Refer to the tables (PORTING SET VERSION VS. BW VERSION NUMBER) for these combinations.

PORTING SET VERSION VS. BW VERSION NUMBER:
porting set version: bw version number:
6.1c.07.11 82
6.1c.07.10 81
6.1c.07.09 80
6.1c.07.08 79
6.1c.07.07 78
6.1c.07.06 77
6.1c.07.05 76
6.1c.07.04 75
6.1c.07.03 74
6.1c.07.02 73
6.1c.07.01 72 "

Any ideas would be appreciated.

Well I have never heard that the bw client is tied to the porting set. Baan has told us on a couple of occasions that we need to upgrade the client with the porting set. At the point we are running B40c.80 and connecting to our service pack test company, which has portingset 6.1c.07.11. At this point I do not know of any issues caused by this combination.

It is a known issue with BW 81 and 82. We logged an issue with SSA Global\Infor and suppose to be fixed in Porting Set 6.1c.07.12/BW 83. You have to use BW 80 or 79.

If you want to keep the BW 82, you have to put -- set USER=xxxxxx in the command line of the BW

Thanks for the information :) . You're right, putting on the 80 client works now. Any idea who at Baan knows this. I'm working with support and it doesn't sound like this is a known issue.

Hi,

Please tell Support to search for Inquiry ID 320326 for MDA Space Missions and the resolution of the case is that will be fixed as part of Porting Set 6.1c.07.12. The SSA Global/Infor person was Chris Snyder.