calling a CVF DLL in VBA and evaluation version

[julesellis]

Hi,

A few years ago I wrote a few DLLs in CVF. These DLL are called in a VBA module in MS Exceland Access. I want thisprogram (VBA + DLLs) to workon another computer, where CVF wasnot installed. For this purpose, Compaq had a tool (VFKIT or something), but after running this (and trying a lot more) the program still didn't work. I always get a message like 'Error 53 Unable to locate file', and this error occurs at the VBA line where the DLL is called, even though the Declare statement definitely contains the correct path and filename. Then I installed (illegally?) the whole CVF compiler on this second computer, and immediately uninstalled it. After this, the program worked. Now there is also a third computer on which theprogram should work.Unfortunately, I'm unable to install CVF there: I get a blue screen. This, althoughthisPC has Windows 2000 NT. Obviously, I cannot get support for CVF anymore. Therefore I am thinking about migrating to IVF.Now I have the following questions:

(1) According to the pdf document about migrating from CVF to IVF, you can use CVF DLLs without re-compiling them in IVF. Is this also true if you call themfrom VBA?

(2) Moreover, the CVFDLLs called IMSL routines. Will the(CVF compiled) DLL still work even though the Standard IVF does not include IMSL?

(3) Suppose that I have to recompile the DLLs. CanI somehow use the IMSL from CVF in IVF?

(4) Suppose I get the things working in the evaluation version of IVF (perhaps after writing some substitutes for the IMSL part). I understand that the compiler will not work anymore after 30 days. But will the DLLs continue to work after this date?

(5) Suppose I re-compile the DLLs with the evaluation version of IVF. Is it allowed to use the compiled DLLs on other computers, and will they still work after 30 days?

[Steven_L_Intel1]

All you needed was the CVF redistributables, which were freely downloadable from the Compaq web site.

To answer your questions:

(1) Yes. In fact, if you're calling the CVF DLLs from VBA, Intel Fortran doesn't enter into the situation at all.

(2) Yes. CVF had only a static library form of IMSL, so the IMSL routines are embedded in your DLL. No problem there.

(3) No. The libraries are not compatible.

(4) By the terms of the evaluation license agreement, no. Here's what it says:

EVALUATION LICENSE: If you are using the Materials under the control of an Evaluation license, you as an individual may use the Materials only for internal evaluation purposes and only for the term of the evaluation time period, which is controlled by the license key code for the Materials. NOTWITHSTANDING ANYTHING TO THE CONTRARY ELSEWHERE IN THIS AGREEMENT, YOU MAY NOT DISTRIBUTE ANY PORTION OF THE MATERIALS, AND THE APPLICATION AND/OR PRODUCT DEVELOPED BY YOU MAY ONLY BE USED FOR EVALUATION PURPOSES AND ONLY FOR THE TERM OF THE EVALUATION PERIOD. You may install copies of the Materials on an unlimited number of computers provided that you are the only individual using the Materials and only one copy of the Materials is in use at any one time. A separate license is required for each additional use and/or individual user in all other cases. Intel will provide you with a license code key that enables the Materials for an Evaluation license. If you are an entity, Intel grants you the right to designate one individual within your organization to have the sole right to use the Materials in the manner provided above.

(5) The evaluation license agreement does not allow you to redistribute the run-time DLLs and you are supposed to stop using the application if the evaluation period expires. There isn't anything in the code that stops you from using your application after the eval period... or is there?

[julesellis]

Thanks for your fast answers. However, your first remark, about downloading the CVF redistributables, is really wrong. I tried this on several occassions with the help of several other people on several different computers and we spend hours and hours on it. The result was always the same: It just doesn't work. Perhaps there is some secret thing that you have to do, but we can not dicover it, even though we read the manuals thoroughly on this point.

[Steven_L_Intel1]

In that case, what you did was build a Debug configuration of the DLL. Those are not redistributable. You need to build a Release configuration.

[julesellis]

That makes sense!!! Indeed, when somethings goes wrong he wants to start the debugger always and a redistributable shouldn't want to do that.I will try it out. Thanks a lot!

Jules

[julesellis]

Hi Steve,

I found out how to build a Release configuration, built one, and... it WORKED!!! GREAT! More specifically, I have two disks on my PC, and I can boot from either one. On the one system I have CVF installed, on the other not. Untill now I could not use the DLL in the system that doesn'tknow CVF, but now I can. So probably this Release version will work on other PCs too.

I must admit that I never saw the part of the documentation about Release configurations.The section about redistribution with VFRUN does not refer to it (at least I didn't see such a reference).

Although your accurate help somewhatreduces my urgencyto buyIntel Fortran on the short term, it increases the probability on the long term. Since CVF is dead, I'll have to migrate eventually, and I think that accurate support is very important. (I don't understand 90% of the CVF help documents, and probably this is the samefor every fortran version). Isaw a lot of the otherthreads, and I see that you are really a super expert. But that raises a question too: If you would go to another company, would this forumthen be dead too? Anyhow, thanks again.

Jules

[Steven_L_Intel1]

Thanks for the compliment. (That WAS a compliment, right? :-) )

As much as some people seem to think it's so, I am not the only support engineer here - even more the case at Intel than at Compaq. Being the "public face" of the Fortran product is part of my job, but if I should get hit by a bus tomorrow, we have several other engineers who could fill in for me here. So don't worry.

Yes, good support is what you'll get with Intel Visual Fortran. We have about a dozen support engineers specializing in Fortran at Intel Premier Support. I feel privileged to work with them.

With Intel Visual Fortran you also get a large team of talented development engineers (the old CVF team plus a bunch of Intel developers), who are constantly improving the product, and superb technical writers who work on the documentation.

[julesellis]

Yes, it was a compliment, I'm impressed. I know that helping at a distance is very difficult, it ususally involves some kind of speculation and mind reading about what's happening at the other side. It seems that you've impressive mind reading capabilities too, since IWAS actually thinking about this bus instead of another company, but then I thought that you deserve a more friendly scenario :-).

About the support staff: Sounds good.

Jules