TCC-RT doesn't have a command line. They're different products with different goals. The main purpose of LE is give a taste--but then you have to buy the carton of ice cream.Management decision was to release TCC-RT.
There's no reason to even look into TCC/LE anymore.
Keep in mind the purpose of putting TCC/LE in the App Store--providing a free taste. "Hey! This looks interesting! ... Let me try it--it is free."I don't feel that necessary. There's better tools for that, than TCC could ever become. It's just whole different league.
Actually, for work I wrote an entire setup in TCC/LE that accesses a hospital's secure FTP site, downloads a pipe-delimited set of records of patients who have been in car accidents, checks the file for bad characters (/, <, > and =), parses the records, maintains a list of EVERY account sent, compares new records against that to weed out duplicates, assigns in-house account numbers for accounts that will be kept, looks up address info, etc., for the hospital and puts that in an output record, looks at wording in the diagnosis description and categorizes the visit, creates two output files, one to be imported into the New Accounts database and the other into the Junk database (e.g., fell off roller skates), flags accounts over $50k, counts and displays the number of good files and "junk" files, combines info from a bunch of fields to create a History field with date account is placed, patient age, dollar amount, diagnosis description, name, address, etc., of any THIRD insurer, and the account number.TCC/LE is not "interesting" - it's useless.
It's not even comparable to native CMD.
|Thread starter||Similar threads||Forum||Replies||Date|
|M||Add "ReleaseID" (aka version or build) to ver output||Suggestions||2|
|J||Declined Even faster screen output?||Suggestions||5|
|P||Done Have option not to pause TCMD console output when mouse is clicked elsewhere||Suggestions||0|
|D||Command Input Feature Request||Suggestions||0|
|R||Done Putting command output into an array||Suggestions||2|