is there a chance to transfer the address of a LabTalk string (e.g. Z, because of its length) to an external DLL? I ask since I am limited in the length of the parameter string which I have to use in my dll command call. So I thought it would be the best just to transfer an address to an appropriate prepared parameter string instead of using it directly in my dll calling.

Thanks for any help.

For example if a DLL has the following function
int FAR PASCAL myDLLfunction(HWND hWnd, LPCSTR lpstr);

and you call this function from LabTalk with
DLL myDLL myDLLfunction %Z

thanks again for your attention.

Funny, although I code C and Pascal already since years the obvious things you don't get. Certainly, it's already an address which you transfer with LPCSTR... :|

But it's a great feature that this way also enables me to access the huge space in %Z!!!

Thanks alot. So I can avoid using a ramdisk for parameter buffering. That's great.

But if I once started this subject, perhaps I could go further in my speculations and imaginations. Is there a possibility to statically store information in a DLL? I mean to initialize my DLL functions with some parameters and still be able to use them half an hour later... This means that the DLL shouldn't be unloaded by Origin in the meantime... Suggestions?

well, I mentioned ramdisk because it would probably the quickest method to get fast access to the data I need to transfer to the dll. Suppose I need to call the dll quite often then it wouldn't be so nice to have it reading all the time on my hard disk. That is why I came to this solution. I mean as long as it would be in the hard disk cache it shouldn't be a problem too.... Don't know.

But anyway. The only problem is that I would have a huge amount of parameters to transfer to the dll. Without the %Z variable it is impossible by now. Luckyly this opportunity exists, so I could also work with that. So I think it is not worth the huge capabilities I could have with MODLL, since the dll function actually computes a certain data set and need some input columns from Origin, but doesn't need interaction between Origin and the dll in this process...

But anyway, maybe for this purpose one could use MODLL though, but then it's the question whether it needs to be bought together with Origin Professional or not? Since I own only Origin 5.0 it would require to upgrade, which is not so necessary.

Okay, thanks for your help. I am really surprised any happy that contact with Microcal is of this high level. Thanks alot.

Somewhere I already saw examples for MODLL, but as I understood the code was incomplete and unusable for me. Also it seemed to me that it is quite complicated to code such DLLs. So maybe I should just go the way using an intermediate file to store information, say on a ramdisk which I would have to install then...

What's your opinion about that?

On the other hand, is it possible to get full source code with examples for the MODLL for O5.0? And is it really that complicated to use?

Okay, that's all so far. Thanks for your quick replies.

Marko

You mention "ramdisk". I understand a ramdisk to be a portion of RAM setup to simulate a disk drive. Is this what you are refering to?