Export to excel on new PC

[cptdave]

Hey Guys,

I was hoping someone might be able to shed some light on a little problem i'm having.

We are in the process of rolling out Windows 7 64bit to all our users and a handful of them have PL/SQL Developer 8.

Our first user to test PL/SQL Developer 8 on the new setup has found she can no longer use the "export table > to excel" function. She can get he query results up on screen just fine, but when she clicks the button, it greys out and looks like its thinking about things, but after a couple of minutes the button just returns to its normal colour without doing anything.

They are using the same version of excel as before (2007)

Sorry I'm not a PL/SQL Developer user (just a tech) but I was wondering if anyone could point me in the right direction.

Thanks
Dave

 

[mike]

This is a guess, but I had to right click on the shortcut and change the properties to run as administrator for several things to work when I switched to Windows 7.

 

[Hilarion]

I have no problems using PL/SQL Developer 10.0.5 on Windows 7 (64-bit) with User Account Control turned on (and set to maximum restrictions) and do not have to run it with full administrative rights (except when I want to change preference sets from default preferences tab). Export to MS Excel works fine too (MS Office 2010 x86).

 

[mike]

Thanks for the information. My guess is likely wrong then. It's been a while, but if I remember correctly I couldn't update preferences, add templates, or use plug-ins that wrote to the program directory. Stuff like that. My guess was that perhaps Excel was trying to write a temp file to a restricted directory and couldn't.

 

[Hilarion]

I made sure PL/SQL Developer writes user preferences in user profile folder by adding this to "params.ini" file:
prefpath=%APPDATA%\PLSQL Developer\Preferences\

In your preferences you can specify where (in what folders) the PL/SQL Developer should store macros, templates, plugins, etc.

Not sure why would Excel misbehave like that. Cptdave could check if "excel.exe" process is started when trying to use the export to Excel function. If it's not, then it's rather PL/SQL Developer issue.

 

[RickG]

I'm having the same problem so I thought I'd check the forums and found this thread. Was there a resolution to this issue?

When getting new PCs, some (but not all) of our PL SQL users cannot use the Copy to EXCEL function. We get the query results up on screen just fine, but when we right click and select the