Andy, Can you give us more details? Does this mean you are only parsing the script part at line 100 leaving the other defaulted items as they are? Can you send us an example?
Thanks, JT -----Original Message----- From: Lee, Andy [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 2:17 AM To: 'U2 Users Discussion List' Subject: RE: SBClient on Windows XP We have had this... Quite a lot of problems on win2k.. where scripts would 'break' and hang at certain prompts.. or like yours, not actually start properly. We have made the scripts more stable by creating them programmatically, as the sbc file is quite easy to parse, its char(254), char(253) and char(252) seperated.. and the script section is from attribute 100.. Since doing this, we haven't had any problems, but it has only been a couple of months, I don't trust SBC scripting just yet.. it is a whacky beast! Andy -----Original Message----- From: Jason Theis [mailto:[EMAIL PROTECTED] Sent: 05 February 2004 14:40 To: 'U2 Users Discussion List' Subject: RE: SBClient on Windows XP Speaking of SBClient. Has anyone seen issues launching an SBClient document session using the below code snipet? Set oSBClientConn = CreateObject("SBClient.SBClient.1") status = oSBClientConn.StartServer(SBClientSession, strParams, 10000, gstrSessionHandle) Note: Variables SBClientSession, strParams contain appropriate values to initiate the SB+ connection. gstrSessionHandle is used for reference to session. We are experiencing script lockups on about 50% of our XP installations and about 15% of our Windows 2000 sessions. By script lockup I mean - upon the call to the proper SBClient.sbc (document) session the script will attempt to start but nothing will happen. The only way I can take care of this issue is to go to help, troubleshooting, reset port. Any ideas would help. JT -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
