topic Sorry - tried to insert an in Intel® Fortran Compiler

f90SQL error in Windows 7 using Compser XE13 in VS 2012

warwickb1 — Mon, 26 Aug 2013 06:50:56 GMT

I get the message

trying to run a program re-compiled with Fortran Compose XE 2013 and re-linked in Visual Studio 2012. I think I am using the Win32 compiler as opposed to the x64 compiler. Should the Win32 compiler work the same as I used before: IV Fortran 10 in VS 2005? I saw (12/28/2010 - 08:58 - <http://software.intel.com/en-us/forums/topic/291932>) that Steve Lionel suggested giving up on f90SQL for 64-bit systems but if I can continue to use a 32-bit compiler that might just have to do for a while! But if the Win32 compiler should be OK any suggestions as to what I need to do to get it working with the DLL?

I have put the DForrt.dll and f90SQLDVF.dll files in the same directory as the executable.

Hope you can help.

Warwick

Sorry - tried to insert an

warwickb1 — Mon, 26 Aug 2013 06:57:30 GMT

Sorry - tried to insert an image - looked OK but did not send. Wording: "The procedure entry point _F()SQLEXECUTRE@8 could not be located in the dynamic linke library f90SQLDVF.dll"

The error message in the

warwickb1 — Mon, 26 Aug 2013 07:09:31 GMT

The error message in the image was:

“The procedure entry point _F90EXECUTE@8 could not be located in the dynamic link library f90SQLDVF.dll.”

Thanks for the screenshot, as

Steven_L_Intel1 — Mon, 26 Aug 2013 15:42:20 GMT

Thanks for the screenshot, as you had mistyped the error message text.

According to the README, f90SQLExecute was not include in the "Lite" edition of f90SQL that was freely available and which we offer a copy here. My guess is that it was in the "full" version that Cainaima sold and which your application linked to. The README suggests using F90SQLExecDirect as a substitute.

Thank you for that. I had

warwickb1 — Wed, 04 Sep 2013 04:29:25 GMT

Thank you for that. I had forgotten that you DO NOT use f90SQLDVF.dll when using the f90SQL Pro version as it supplies its own f90SQL.lib. I had both specified, hence I got the error. I also had to discover how to connect to the Oracle 32-bit driver on my new Windows 7 machine after installing the latest Oracle Client. Only the default 64-bit drivers are shown using the version shown in the 'START > All Progams' list. It is necessary to run the 32-bit Microsoft ODBC Data Source Administrator using 'C:\Windows\SysWOW64\odbcad32.exe' to show the 32-bit drivers and hence assign to a DSN.