Missing DLL running f90SQL ModuleWizard on new PC

[warwickb1]

Hi, On my new PC, when trying to run the f90SQL Module Wizard, I get the error message = " Run-time error '48': Error in loading DLL ." Similarly, for SQLEditor, ModuleEditor and DBExplorer. For the QueryAssistant I get the error message = " Run-time error '91': Object variable or With block variable not set. " I use Intel Visual Fortran v10.0.025 and Visual Studio 2005. I have included dforrt.dll into the %System_Root%/system32 directory and included the F90SQL.lib into the compiler's lib directory. My Path Environment Variable is as follows :- " C:/Program Files/Intel/MKL/9.1.025/ia32/bin;C:/oracle/product/10.2.0/client_1/bin;%SystemRoot%/system32;%SystemRoot%;%SystemRoot%/System32/Wbem;C:/Program Files/Windows Imaging/;C:/WINDOWS/system32/WindowsPowerShell/v1.0;%IFORT_COMPILER10%/IA32/Lib " - and the files cswDefODBCConn.exe + cswNameServer.exe + cswServices.dll + DBExplorer.exe + frt.dte + ModuleEditor.exe + ModuleWizard.exe + QueryAssistant.exe are all in each of the directories C:/Program Files/Canaimasoft/f90sql + C:/Program Files/CanaimaSoft/f90sql/f90SQL + C:/Program Files/f90SQL/f90SQLWizard + and the same errors occur in each one. Immediately after the first install of the Module Wizard, one of the programs actually worked - I think it was the DBExplorer. Unfortunatley, as I made changes, I didn't check that this still worked. On my old machine I noticed that along with dforrt.dll in the Windows/System32 directory, I have Dfdlg100.dll + Dformd.dll which have the same Modified and Created Dates as for dforrt.dll, but I don't know where I got them and they don't help. I have also defined Environment Variables : "f90SQLDVFLibDir = C:/Program Files/CanaimaSoft/f90sql/lib " + "f90SQLDVFModDir = C:/Program Files/CanaimaSoft/f90sql/mod " with dforrt.dll + f90SQL.lib also in the f90SQLDVFLibDir directory and f90SQLDVFModDir contains the *.mod files. Short of undoing everything and starting again, I am hoping that someone might have some ideas to try, as I seem to have run out of them.

[Steven_L_Intel1]

That's an error from Visual Basic. Is this "Module Wizard" something that's part of the f90SQL product itself? As far as I know, DFORRT.DLL is needed only when you run your application.

[warwickb1]

That's interesting. To me that implies that I need to re-install my Visual Studio 2005 in the hope of re-establising Visual Basic. However, there is very little of reassurance in the VS2005 ReadMe about what should (or should not) be uninstalled first. For instance, it says to Remove 'Microsoft SQL Native Client' but I don't have that but I do have 'Microsoft SQL SERVER Native Client'. There are other similar conundrums. I have sent a query about this to the Microsoft Forum, but no reply as yet.

Perhaps I need some test of VB to see if it works OK?

The "Module Wizard" requires a separate installation. When working it can create a Fortran module that performs a particular query. It may well be independent of DFORRT.DLL.

Thanks for your reply. Unfortunatley there is no longer any support from Canaima for this product. I suppose I can just modify the modules I have already, if necessary, to do any new tasks.
Regards, Warwick

[Steven_L_Intel1 · Accepted solution]

I never used that part of f90SQL - I'd be astonished if it required VB to be installed. It might need some sort of VB redistributable package.

[warwickb1]

In Microsoft's Visual Studio forum, the suggestion was made to try Microsoft's Process Monitor.

Thanks to Process Monitor, I found an attempt to use a messy file pathway reference that was associated with a previous installation of the application. It no longer existed as I had tidied it up. Not knowing why it doesn't get corrected when Removed (with the Add/Remove tool) and then re-installed, I just re-created the old directories so that the pathway pointed to somewhere that now exists. Pleased to report that all the application Wizards now work. Therefore everyone was correct that it was NOT a VS installation problem. As a result I don't have to take the risk of making things even murkier by re-installing VS.

Thanks for your assistance in giving clues about where the problem wasn't!!