This content has been marked as final. Show 8 replies
What problem do you have trying to use it? I havent tried it myself but dont know of any reason it shouldnt work.
Apart from the "nothing is certified on Windows 7 yet" scenario, I don't know any reason you couldn't use oo4o like usual if you've got the other stuff installed and working and don't care that it's not supported.
One caveat of course is that oo4o is 32-bit only, and there are no plans to port it to 64 bit. So if you're on an x64 box you'd have to install a 32 bit Oracle client, configure an IIS app pool to run as 32 bit, set VS to compile as 32 bit for forms, etc. A 32 bit home and a 64 bit client home play rather nicely together though so that doesn't cause much headache. If you've already got a 64 bit client installed, just add 11107.20 ODAC into a new home and you should be good to go.
Hope it helps,
The problem is just that the installers get the heeby-jeebies when they see that the host operating system's version is 6.1, and refuse to install anything. For instance, the installer "ODTwithODAC1020221" opens a console window and then quits with the message "Checking operating system version: must be 4.0, 5.0, 5.1, 5.2 or 6.0 . Actual 6.1".
AHA, I've found the check: it's in a file called oraparam.ini, so now I'm past that test and the installer is running. I think it worked.
Well, the installer ran, but the VBScript still fails on CreateObject("OracleInProcServer.XOraSession").
The installer shows it to be installed though, and you have oip10.dll in your OH\bin?1 person found this helpful
Are you running 32 bit vbscript or 64 bit?
Where are you running the vbscript? IIS? Did you configure the app pool to be 32 bit?
Try this from a dos prompt.. put this in c:\testoo4o.vbs
try it, making sure to run it as 32 bit (via using the cscript.exe in syswow64)..
'''c:\TESTOO4O.vbs Set osess = CreateObject("OracleInProcServer.XOraSession") Set odb =osess.OpenDatabase("orcl","scott/tiger",cint(0)) Set ods = odb.DbCreateDynaset("select sysdate from dual",cint(0)) v_sysdate=ods("sysdate") ods.close odb.close wscript.echo "sysdate is" & v_sysdate
hope it helps,
The DLL is there, and I did not have the app pool set to 32 bit. Giving it a 32 bit application pool in IIS got it to a third failure mode: now it hangs forever with no error message.
The test script executed successfully! So OO4O is apparently usable, and it's just a matter of getting IIS/ASP to see it.
...no sweat, all it needed was another reboot. So your application pool suggestion was the answer.
 I tried to mark your answer as the answer, but it's still just showing as "Helpful".
Have you checked compatibility?
Just an FYI for you.
It is always best to check with the software manufacturer FIRST. They will tell you if they have tested the product and the version, as well as whether or not it will work with Windows 7.
Check out the Windows 7 Compatibility site: (There you will find out about hardware and software compatibilty.)
There is a pulldown from which you can choose "hardware" and "software".
There are also some great articles, instructional videos and such to help with your Windows 7 at our Springboard site:
In any event a lot of the times, Vista drivers will work in lieu of Windows 7 drivers, however, it's not 100%!
As stated previously, it's best to have the Windows 7 certified drivers installed.
Microsoft does have an official Windows 7 Support Forum located here http://tinyurl.com/9fhdl5 . It is supported by product specialists as well as engineers and support teams. You may want to check the threads available there for additional assitance and support.
Microsoft Windows Client Support