[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:	TeamLinks for Windows
Notice:	Kit and ECO locations: See replies to note 8.o note 8.
Moderator:	ORION::chayna.zko.dec.com::tamara::eppesAN

Created:	Mon Aug 28 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2238
Total number of notes:	9650

2032.0. "Reply insert spaces in front of TO addresss" by UTRTSC::SMEETS (Workgroup support) Wed Mar 05 1997 06:14

Hi,

I've a customer running TeamLinks V2.5 Dutch with ALL-IN-1 V3.1 report a
similiar problem as described in topic 1728. The only difference is that this
customer can reproduce the problem and instead of 2 spaces they get 6 spaces.

The problem is reproducible as can seen below:

The first time the customer starts TeamLinks ( I don't know if it is the first 
time of time) and wants to reply to a message than there are six spaces added in
front of the TO address.

The next time the customer tries to reply to the same message than there are no 
problems.

Has this problem ever been solved ?

Martin

T.R	Title	User	Personal Name	Date	Lines
2032.1	Reproducible scenario	UTRTSC::SMEETS	Workgroup support	`Wed Apr 02 1997 08:52`	22
	Hi, I've received some more information from this particular customer. The adding of the six spaces ONLY happens if this user tries to reply to a message received from a Mailworks user. It doesn't occur when the sender is an ALL-IN-1 user. Futhermore this applies to EVERY message received from a Mailworks user. It's also reproducible by the user. 1. He selects a message from a Mailworks user and select the reply button 2. In front of the TO address there are 6 spaces inserted 3. User cancels the reply operation 4. User replies to the same message and now the problem doesn't occur I've asked the customer to enabling tracing when performing the above scenario. Has anybody an idea what's happening here ? Martin
2032.2		XANADU::cascobay.zko.dec.com::TAMARA::STJEAN	Bob St.Jean	`Wed Apr 02 1997 10:41`	8
	Martin, I brought this topic to the attention of the here developer who handles mail addressing issues. He loves mysteries like this. Of course he also likes digging up rocks on his farm... I don't know which thing he likes to do better. I suspect it's the rocks. Bob
2032.3	Need some rocks ?, no problem...	UTRTSC::SMEETS	Workgroup support	`Wed Apr 02 1997 11:04`	10
	Hi Bob, Maybe I could print out the CFCDEBUG.LOG but it into a box include some rocks and sent to the developer 8-).... But enough jokes. As soon as I receive the CFCDEBUG.LOG I'll make it available. Regards, Martin
2032.4		XANADU::cascobay.zko.dec.com::TAMARA::STJEAN	Bob St.Jean	`Wed Apr 02 1997 16:14`	7
	Martin, I'm not sure if the CFCDEBUG log will show us anything with this type of problem. Bob
2032.5	Corruption in office.ini ??	UTRTSC::SMEETS	Workgroup support	`Mon Apr 21 1997 07:12`	9
	Hi Bob, After the customer enabled the CFCDEBUG.LOG the problem didn't show up anymore. So I guess there was something wrong in the office.ini. After editing and saving this file the "corruption" disappeared. Regards, Martin
2032.6		XANADU::cascobay.zko.dec.com::TAMARA::STJEAN	Bob St.Jean	`Mon Apr 21 1997 17:53`	5
	Changing the logging options seems like a pretty strange way to make an addressing problem to disappear! Bob