|
PureBytes Links
Trading Reference Links
|
Mark,
I didn't have that problem when being pushed another upgrade but I didt have systems and indicators broken that worked for 2 1/2 years under TS2k and even prior versions of TSpro (see my message "Thank you for taking the time to send us your inquiry..." sometime on Saturday). BTW, that subject line is part of omega's standard "cut and paste" email response from a support droid *several days* after you've received the email server's automated confirmation receipt of your email.
The beauty of TS2k and TS4 is that you *could* roll back to a prior release should you encounter problems with an "upgrade". With TSpro - you're dead in the water should you encounter *any* problems. You can't roll back and you can't get any fixes from omega. You'd better be up to date on your nightly back ups and hope that you discover the problem before you recycle your tape.
TSpro is *constantly* changing with each build. These upgrades aren't simply bug fixes. There's major restructuring of the product. Legacy product behavior and functions have been changed and/or broken in mid-release. The only response from omega is that they're aware of it and it'll be addressed "in one of the future releases".
My rare encounter with omega's tech support doesn't leave me with any confidence in the product and certainly not to open a 50K minimum trading account with them. Hell, I can piss my money away as well as they can.
I have been looking into the TS2k/Dynastore/Qfeed combination over the weekend. The one time purchase of Dynastore/Dynaloader combination is 350.00 and QFeed is 79.95 per month. This is very reasonable for me. Monthly is less than TSpro and I have a product that has stabilized with known bugs instead of constantly getting new ones on each "upgrade" that is pushed to me.
Good luck....
-- Roy
Mark Jurik wrote:
> A few days ago, TS Pro on my computer notified me that Build 304 is available, requiring an automatic upgrade. I let it happen. Immediately after upgrading, I noticed many user defined functions that were previously verified were now not verified. The VERIFY ALL command could not remedy the problem. Those files that were tokenized (no source code available for editing) could not be repaired and had to be deleted and re-imported. During re-importation, a dialog box notified me that the function I was about to replace was modified the same day as the upgrade. Since I knew that function was not changed by me, (it was a tokenized file), one can only conclude it was modified during the auto-upgrade to Build 304.
>
> Omega tech support admitted that TS Pro auto-upgrades "may" destroy linkages that prevents studies from verifying, requiring the study to be deleted and re-created or re-imported. So I strongly recommend periodic archiving of all your important studies, just in case an auto-upgrade modifies your functions and/or degrades a linkage that prevents simple re-verification.
>
> However, there is another problem. TS Pro exports ELD files, which (on my machine) produces code that has problems when re-imported back into TS Pro. It appears that after I import function "X" from one ELD file, then importation of an unrelated function "Y" from another ELD file has forced function "X" to become unverified. I see no logical reason for this, except that some linkage is messed up. VERIFY ALL does not remedy this problem.
>
> The only way I found to clean up the mess (temporarily) is to delete about 30 studies, then run VERIFY ALL, then re-import my studies as ELS files from TS 2000i. It seems that functions from ELS files behave with more stability in TS Pro than those from ELD files. I have no idea why.
>
> PS -- there is some humor here ....
>
> When I asked TradeStation tech support when they would fix this problem, especially when an auto-upgrade could potentially disable a trading systems already in use, the person recommended I submit my bug report to their "wish list" at tradestationwishlist@xxxxxxxxxxxxxxxxx Isn't a wish list for optional bells and whistles?
>
> Mark Jurik
|