nick_rogers
7th April 2004, 20:59
Just upgraded to Porting set 6.1c.07.03 from 6.1c.06.04
Also have the new BW Client c.74

Opened Baan case to see if any tools objects needed upgrading, they said NO.

We have an important interface session that reads an ASCII file and populates some tables. The session has been used for 4 years, after installation of the new porting set 6.1c.07.03 the session no longer works. During debug the problem is identified with the function seq.gets() no longer working as expected.

Details:
first line is read in correctly,
second line is read but the first character is not present.

example:

first line is "12345"
second line is "2345"

Anyone encounter this ? also anyone know what tools component the seq.gets() resides in ??
OmeLuuk
10th April 2004, 14:16
Looks familiar to me. There has been a problem *(not portingset related)* with ASCII files. Search the knowledge base on CLIEOP (ASCII payment files for electronic banking).
nick_rogers
14th April 2004, 19:41
Hi I did a search on CLIEOP and found nothing.
mark_h
14th April 2004, 19:58
Baan has just requested that we update our client and porting set to those that you mentioned. I have loaded and am running the client without any problems. I will keep you posted if/when our admin updates the porting set.

Mark
nick_rogers
15th April 2004, 22:51
Mark- I would test the interfaces in test area first....if you don't already...............
mark_h
15th April 2004, 23:22
I talked to the admin yesterday and he is not wanting to install the porting set. I am not sure that is a good idea. ~Vamsi once told me we need to keep these things in-sync and we haven't.

Mark
nick_rogers
16th April 2004, 16:18
I think in the future that I will wait several months aftr a port set is released before even looking at it , it seems as though things get broken on every release with new bugs introduced.
dnnslbrwn
16th April 2004, 16:28
I had a client where the CIO was very "bleeding-edge". Every month we got a new toy/software package that was broken simply due to how new it was. I feel your pain :)

Dennis
nick_rogers
16th April 2004, 16:31
Dennis - I will send youre script this morning......
OmeLuuk
20th April 2004, 00:31
The problem was caused by solution 140675 and fixed in 140839.
nick_rogers
3rd May 2004, 22:46
Finally got some answers, there is now a bug on this new version of the porting set and logged as defect # 219566 - seq.skip function not working per programmers manual.

Not sure if the seq.skip is used in the Exchange module...is so then Exchange schemes migh not work anymore.