SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Non-Tech : TD Waterhouse Group (TWE)

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Barry Moss who wrote (1023)12/25/1999 7:16:00 AM
From: OldAIMGuy  Read Replies (1) of 1413
 
Hi Barry, I think you are right about the Tax Loss Selling going on right now. It might even be holding the price down artificially with supply exceeding demand.

I nearly doubled my position recently as money came out of the buy-out of Hambrecht & Quist shares I owned. I'll continue to trade around this new core. The range is set up to add about 5% to the holding in the low $14s and sell off about 5% if the price hits about $19 (US). This probably looks like a rather fat range for most ST traders, but this is a different method.

My initial position wasn't in the IPO. I fortunately messed up and didn't get any at $24. :-) However, when the price sagged into the mid teens it looked like the time to start. Bought the initial position there and then added to it as the price continued to decline to between $11 and $12. There's only been one sell so far.

As TWE continues to expand there's going to have to be some "infrastructure" changes to solve problems like have been mentioned here (20 minute waits, etc.) but their pockets should be deep enough to afford this. I mostly trade on-line and that's been just fine most days. Most of my trades are limit orders set good for 60 days. So it's a bit lower key than the ST Trading group. I can understand frustration in having to wait - especially over a mutual fund transaction. Hope it gets better for you.

Best regards, Tom
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext