No, it is not okay to use the Write version unless you pay for it. You may contact Equis sales for more information.

Same reason as your last post. You're using Read/Write functions (MSFL1_AddSecurity) and probably only have the Read Only version of the MDK.

That is a function available for the Read/Write copy of the MDK. My guess would be that you're using the Read Only version. The Read Only version is not able to create or modify securities or security folders.

The pointers to MSXDataRec are probably being deallocated at the end of the call to the MSX DLL, since there's no point to keep it around. It's not a threading issue. You're not supposed to be holding onto pointers, since they're not guaranteed to still be there in a different call. You'd be better off saving the actual data you were passed ...

Ah, okay. That makes sense. No, what I was saying wouldn't apply then. MetaStock's MSFL would be the only copy accessing folders. Your problem then would be how you go about knowing which structures are open and still valid. When MSFL (whether from MetaStock or MDK) is writing to a data file, it must lock it and make it so other instances of MSFL ...

If your DLL isn't using MSFL, how is it trying to get data from another security?

I don't know what you mean by MSK. I had been guessing that meant MetaStock. Yes, if MetaStock 9.2 is accessing the folder, MSFL from MDK will not be able to (and vice versa).

Yes, some of us visit the forum. My first guess might be that your copy of MetaStock and the MSFL from your MetaStock Developer's Kit are different versions. One version of MSFL cannot access a folder locked by another version of the MSFL. Your stand alone app is probably the only version of MSFL running on that folder at the ...

Also, two different versions of the MSFL can't access a folder of securites at the same time while two programs using the same version can.

There will be some compatibility issues between older and newer versions of the MSX (a part of MDK). The MSFL will probably have fewer issues since the file structure has largly remained unchanged. Your older version would be limited to smaller number of securities per folder (depending on the version you really have, it could be 256 securites ...

Hi all. It's been a long time since I've visited this forum. I hope everyone is doing well. This is in NO way related to Equis or Thomson Reuters. This is something I've done on my own time. I rereleased my stock themed game and thought the people here might be interested. It's for the iPhone/iPod Touch and is a twist on Missile Command. You try ...

It does nothing with the symbol database. The idea of this utility was to use the symbol database to take care of add, removing, and renaming files, but turned out the code for the symbol database is just far too complex to put into the utility. It doesn't look at the symbol when deleting based on x days not traded. So it wouldn't matter if it was

It may be something considered in a future version. Send it as a suggestion to support or post it in the suggestions for MetaStock thread. Unfortunately, there isn't anything I'm aware of that will allow you to do it currently.

That is not currently possible with the MDK.

You could have your MSX DLL make a temp file or something that keeps track of the points. Or the slow route would be to calculate them again, each time. As for your MSFL questions, the app name and user name can be whatever you make up. They're just to identify apps from each other when they access a folder of data. Put anything in them you want ...

I haven't used the MetaStock Formula Language in far too long to tell you whether you can do this in that or not. With an MSX DLL, you can pass in all the data you need (Open, High, Low, Close, Volume). As you do your calculation, the data is in an array and you can go back data points all the way until the beginning of the data. So you can use ...