Hello all, first of all i would like to say that i am not a programmer (at all) and the things i learned after starting using Metastock for 1 week now are a bit too overwhelming sometimes. So any help would be appreciated. Right now i am using an excel file to create indicators, experts, systems appropriate to my own thinking. I use excel to speed up the writing, but then i have to copy-paste every bit of formula to the appropriate place in the Metastock builders. I know i can export the formula from Excel in a txt format.

1)Is there a way to automatically import the txt formulas in Metastock?

2)Maybe convert to the appropriate metastock dat format to import with Organizers?

3)Or even better a file that can be copied directly to the Metastock folder and then the program can use it?

Any of the above would help me greatly. Thank you in advance,

Termi

hey termi.... there is no way known to me to import text itself and have it automatically placed in the proper location.... cut and paste is just about the only route.....

once you spend some time with meta you might find it easier to use the indicator builder, expert builder and so on , as opposed to excell..... those builders have direct links to all functions, dll's and such..... using excell you'll be bouncing back and forth......

some might use notepad but that was often due to the small work areas in prior meta versions.... the work areas in v10 is limited only by your monitor size .....

it might not be apparent now, but when it comes to indicator, experts, explorations or system creation, the builders are the solution ......h

hey termi.... the available character space is pretty much a done deal until equis boosts it up some.....

we can break the large formula up into small parts creating a indicator for each ...... then use the fml function to call that entire block of code but use only a few characters....

it's hard for me to envision running out of space, nothing of mine is that elaborate..... but there's a good chance henry and roy have both succeded in stuffing the code box flat full.....

here is a good example of henry breaking things down into 6 seperate indicators and then later calling those parts with fml("a1"), fml(a2"), and so on in the option strike indicator.......h