If for some reason we have to go to the 32bit client, would we just have to change the registry? It just uses whichever Oracle home is selected on the login screen – and it will be auto-selected if there is only one of the same bitness as Toad. Or Unsubscribe from Toad for Oracle - General notifications altogether. Just make sure that if you decide to run 32-bit toad on windows 64-bit that you use the 32-bit oracle client. If for some reason we have to go to the 32bit client, would we just have to change the registry?įrom: Bert Scalzo [ Thursday, Janu11:22 AM We have enough issues.) If an Access file is needed, we will use Excel as an intermediate step. (We really don’t want to change the installation process.
Our ORACLE_HOME in the registry uses the 64bit path. IT installed both 32bit and 64bit clients (c:\Oracle_圆4 and c:\Oracle_x32). Just what I needed along with John’s comment. To reply, please reply-all to this email. If we have to go back to 32 bit Toad, what Toad limitations are we facing under Win7? Is there a Blog or paper discussing this issue? If so, where is it located?
We are looking into getting the 64 bit redistributable engine. It must be the same bit version (32 or 64) as Toad." Exporting to Excel works fine. This is not the full Microsoft Access product, just the redistributable engine. We get the following error trying to export to Access: "Could not load the Microsoft Access Database Engine. We loaded 64 bit Toad (12.1.0.22) onto a Win7 computer.
Of course the company I work for is in panic about moving to Window 7 from XP. This was recently discovered and it is fixed in beta.Īs a workaround, if you export with the. We tried the suggested workaround, but got the same error.įrom: John Dorlon [ Thursday, Janu9:23 AM
0 kommentar(er)
