Re: [Firebird-net-provider] DDEX 2.0.6 release

2012-09-04 Thread Miroslav Hrázský
Is there any reason to move FB DDEX registry keys from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\ to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\ ? I'm curious because for me (Win7 64) the former works without any problems. On 4 September 2012

Re: [Firebird-net-provider] DDEX 2.0.6 release

2012-09-04 Thread Jiri Cincura
On Tue, Sep 4, 2012 at 1:51 PM, Miroslav Hrázský mhraz...@gmail.com wrote: Is there any reason to move FB DDEX registry keys from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\ to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\ ? I'm curious because

Re: [Firebird-net-provider] DDEX 2.0.6 release

2012-09-04 Thread Mark Rotteveel
On Tue, 4 Sep 2012 14:02:37 +0200, Jiri Cincura disk...@cincura.net wrote: On Tue, Sep 4, 2012 at 1:51 PM, Miroslav Hrázský mhraz...@gmail.com wrote: Is there any reason to move FB DDEX registry keys from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\ to

Re: [Firebird-net-provider] DDEX 2.0.6 release

2012-09-04 Thread Jiri Cincura
For me any of HKEY_LOCAL_MACHINE didn't work. Don't know. Maybe MS changed something. DDEX is such a foggy area. -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com -- Live