Dll OK with CVI6.0 but NOK with CV8.01

[sebi]

hello.
I've updated my LabWindows 6.0 by 8.1.0.
I have had a projet to make a dll.
I cannot use the new dll compiled with cvi8.1 (compile OK). The message is :"the entry point of the procedure xxxxx is not found in the dll..."
Can you help me?
Thanks

[JonathanN]

Hi sebi,

Read through the Receiving Procedure Entry Point Error in CVIRTE.dll with LabWindows/CVI KnowledgeBase and see if that helps. If not, please let me know and provide a few more details like

- Did you make sure to export your functions in the Target Settings dialog?
- Are you trying to call the DLL from that the same machine you created it on?
- Do you have any child DLLs associated with your top-level DLL?

Best Regards,

[sebi]

Hello Jonathan,

I removed CVI6.0 and install cvi8.1.0.

1) Yes, All symbols are marked
2) if i use the source without using Dll Main, that's OK.
3) This DLL uses 3 other DLL.

I include some image of the code.

I don't understand. I copy the project under CVI6.0 with another PC, it's ok, i can use the dll.

Thanks,
Best regards

[JonathanN]

Hi sebi,

I am little confused by your statement "I copy the project under CVI 6.0 with another PC, its okay, I can use the DLL". Are you saying that you take the CVI 8.0.1 re-compiled and built DLL that needs a CVI RTE of 8.0.1 and higher, take that to a machine with just CVI 6.0 on it, and call that DLL from a CVI 6.0 app and it works?

Can you call that CVI 8.0.1 DLL from a CVI 8.0.1 executable?  By that I mean write a small CVI 8.0.1 exe that just calls the CVI 8.0.1 DLL.

Would it be possible to post a reduced down version of the DLL so I could try it out? From the snapshots the DLL looked complex so I don't know if that's possible?

Could you also post a screenshot of the exact error just so we have the exact text?

Are your 3 dependent DLLs located in a path that Windows can find them? The directories windows searches for DLLs in

1. The directory where the executable module for the current process is located.
2. The current directory.
3. The Windows system32 and system directories.
4. The Windows directory.
5. The directories listed in the PATH environment variable
   

Maybe that error message is referring to a child DLL of your main DLL. You could use dependency walker to determine if you are missing any DLLs that are statically linked.

Let me know your thoughts!

Best Regards,