NASTY SHOWSTOPPER--DLGINIT suddenly fails completely

[Intel_C_Intel]

Things were going fine until my last compile. DLGINIT is now returning false for everything. I thought it might be related to my re-installing CFV to test somethign, so I uninstalled it, deleted all related files, uninstalled Intel 8.0, rebooted, ran registry mechanic, reinstalled Intel 8.0. Cleaned solution.

Resource.h, resource.fd resource.rc all look fine.

Still get the problem. Where do I go from here? This project is otherrwise 99% ready for release and I can't do anything.

Can anyone suggest a strategy to recover?

[Steven_L_Intel1]

Hard to say without seeing an example. CVF won't have any effect at all on this. Have you sent an example to Intel Support?

Are you sure that DLGINIT's declaration in module IFLOGM is visible? I wonder if it's being implicitly typed as REAL.

[Intel_C_Intel]

Can't see how it's a problem, since nothing changed in that part of the code--happens for whichever dialog I substitute. This is thousands of lines of code, many megabytes. If I don't get anywhere soon, I'll try and make a sample, but it's always been difficult to get something small from this code (it's roughly equivalent to SPSS and SAS). A Small example mightnot show the problem...I'll try. Can one just copy over the resource (.rc) file to a new project?

I'm installing it on another platform to see if that fixes it. Otherwise, I may have to try rebuilding the project anew.

How can I check if it's suddenly getting implicitly typed, and how can I tell if it's visible or not?

I did do a global replace of "'0****""to"'" before the problem arose, but that's all, and none of it's in the code executed before the failure. Before the last build it all worked perfectly.

[Intel_C_Intel]

Well, what it took was a re-installation of visual studio.net. I can only surmise that the CVF installation screwed it up somehow....

Thanks, Steve, anyway, for the quick response.

[Steven_L_Intel1]

If you have a USE IFLOGM (or USE DFLOGM), it should be ok.

It might be useful to call GetLastError (from IFWIN) and see if it comes up with anything useful. You could also try this - add dflogm.f90 to your project, build in a debug configuration, and step into the DLGINIT code to see what goes wrong.

You can copy the .rc to another project.

[Steven_L_Intel1]

The CVF install would not do anything to VS.NET. But perhaps something got corrupted elsewhere. Who knows. Glad you solved it.