Re: Informix 7.1 and Powerbuilder 4.0

RJ, All my experience so far has been with PowerBuilder 3.x and OnLine so take this with a grain of salt. I'm not quite sure I understand your scenario. You state that your PowerBuilder developers get a 255 when trying to connect. But, you then state that you can connect with PowerBuilder on a friggin PC. I'm not sure I understand why you can connect with PowerBuilder but they can't. I'm sure I'm misunderstanding something. (Or, maybe you need to buy more PC's from that friggin company :) That said, though... My wild guess is that PowerBuilder is stepping onto itself transaction-wise. For some reason, PB thinks it's in a transaction when it really isn't. One thing which ~might~ cause this is a bad AutoCommit value within PowerBuilder. The PB 3.x versions expect this to be set to 1 (True), any other value causes problems (even though the documentation states that it is ignored for Informix). You might also try an "onstat -g sql <PB session id>" command to see what statement was being executed when the error occured. With luck, either the current SQL or last parsed SQL will show you the statement which was executing when the 255 occured. Good luck from another unix biggot! --Craig (craig@chemistry.utah.edu) P.S. You might also check into the StayConnected value... > > Can anyone explain the following scenerio: > > - drop the database > - recreate the database > - (add the pbcat tables, which are never used > [at least there are no rows stored in these tables]) > > - the Powerbuilder Developers then get a -255 error when trying to connect > to the database > > - I then have to find a friggin PC that has Powerbuilder loaded on it > and connect to the database. (Yes I am a UNIX biggot) > Once this is done, the Powerbuilder Developers can connect to the database. >