Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : Datek Brokerage $9.95 a trade -- Ignore unavailable to you. Want to Upgrade?

To: pae who wrote (15731)	2/21/2001 5:57:43 PM
From: pae	Respond to of 16892

Disappearing "Trying to cancel" message. Soes and/or Datek periodically has system problems that prevent an order from canceling immediately. Many of you know the drill: submit an order and only some or perhaps none of the order executes even though it is/was marketable. So what do you do? You could call to whine immediately, but you probably are more inclined - and may even be obligated to - force execution before the price moves too far. So you check "cancel immediately" and click "cancel checked orders" only to slide into "trying to cancel" limbo. Eventually you submit another order and get the job done, but you are going to have to talk to someone to get it straightened out. Now the "trying to cancel" message is initially useful with an appropriate timestamp. But when the order finally cancels (or executes) the initial "trying to cancel" message disappears, leaving you only with the "cancelled" or "Executed" message. So when you are on the phone trying to get an adjustment, you don't have a handy timestamp for your submission of the cancel request, leaving you with incomplete information ... and possibly looking foolish. I know this AM the "Cancelled" message was timestamped 30+ minutes after I submitted the cancel request. (SOES problems.) I did get it taken care of and Datek's various reps were all professional and courteous. My point is this: I think it would be better to leave the "trying to cancel" message on the messages page in order to better assist us in reconstructing what went on. Of course, 90+% of the time the "Canceled" or "Executed" would be simultaneous with the "Trying to cancel", but for those few problem trades when those messages are NOT concurrent it sure would be helpful. What do you think? Should I/we make this request of Datek? (And how do we do that anyway?) Regards, pae

To: pae who wrote (15731)	2/23/2001 5:04:58 PM
From: Terrance Dignan	Read Replies (2) \| Respond to of 16892

I have been using Super express as well as your modified screen and have a question. I would like to have a express order screen open for two separate trading accounts. However, once an account is open, the same account is accessed automatically when you open a second SuperExpress screen. Is there a way where you can direct the 2nd SuperExpress screen to access another server so this can be accomplished? Any advice is appreciated.

To: pae who wrote (15731)	2/26/2001 12:15:58 AM
From: John Waddell, Ph.D	Read Replies (1) \| Respond to of 16892

Modified Super Express Extended Hours Entry Screen Thanks PAE for referring me to your extended hours entry screen and giving me some suggestions for modifying the HTML code. Below are some ideas for modifying either PAE's or the original Supper Express entry screen. The modifications are made on the file: se_order.htm If you want fewer or more order lines on the screen, you can do a search for CreateOrderForms. When you come to CreateOrderForms(#) - where # is the number of current lines - you can simply change that to whatever number you want. As you know, Datek will only allow Limit orders after hours. So, if you try to enter a market order with Duration set to "Day + Ext. Hours" - even during the day - Datek will send you an error message. I've been using Tai Jin's excellent Express Trader. He has many things automated, and has set up his form so that if you enter a Market order, it will automatically change the order type to "Day". I have set up Super Express with the same feature. This way, if you switch from Limit to Market and forget to change the Duration, your order will not be rejected. As the form is set up now, if you switch from a Limit to a Market order without deleting the price, you get an error message. Often, when I need to get out fast, I switch to a Market order. The last thing I need at that moment is an error message. On the other hand, on more than one occasion I have forgotten that I switched from Limit to Market, entered a limit price and was executed below where I wanted to be. The best solution I was able to come up with was to let the error message come up, but have the program automatically reset the price to Blank. If I'm trying to enter a Limit order, I usually have time to re-enter the price, and if I was entering a market order, I can now execute it immediately after exiting the error message - without the added hassle of selecting and deleting the price. This particular change may not be of much use to most people, but when I'm in a hurry to get out, every step saved helps. Below is the code for making these changes. I have put it in the "Sanity checks" section. Please note this caveat: I am new to writing HTML code. I tested the form with these changes over the weekend. Both the form changes and the messages I got back from Datek were what I expected. However, I cannot vouch for these changes. I'm going to use the revised form this week. If I run into any problems, I will post this. Finally, I want to thank jmedved and Ephraim F. Moya for also responding to my request for an extended hours screen. ------------------------------------------------------ // Sanity checks <snip> // Resets the price so a market order can be put in immediately. if (e['ordtype'].options[0].selected && Trim(e['price'].value) != '') { alert('I\'m confused: you selected "Market", but entered a price!'); e['price'].value = ''; e['price'].focus(); return; } // If Market is selected, change "Day + Ext. Hours" to "Day". if (e['ordtype'].options[0].selected && e['expire'].options[1].selected) { e['expire'].options[0].selected = true; }