Dumping data very fast

 No Responses »
Aug 062011
 

Too bad my comment on the original post was deleted. Perhaps they don’t want to know what I had to say, or they don’t like C#? From the top of my head I wrote something like:
The original post.

I created a very simple C# implementation, a console application with hardcoded username/password and select-statement. It roughly has the same speed as the Pro*C (C routine) version, about 1.7 million ALL_SOURCE records in about 57 seconds. C# is a little more appreciated amongst managers, since C# developers are a lot easier to hire than Pro*C developers. Why on earth you want to fiddle around with Java when something needs to be done fast, puzzles me. Even Java 6 (don’t know about 7 yet) does not come close to the performance of .NET, let alone natively compiling languages.

Data binding pitfall

 No Responses »
May 122011
 

I have been struggling with a databinding problem in WPF/XAML. To have some screen fields automatically update a class, I bound them to instantiated class (let’s call that myEmpData). In the XAML file I defined the path and source for each component to point to the class and a property in that class. The pitfall is that this creates a scoping problem. I could see the validation rules do their work, since my textboxes turned red whenever I entered incorrect values. But the underlying class was never changed. Or so it seemed.
I found out that you have to define your binding source as high as possible, I did it within the PAGE definition. Binding textboxes (or other components) to this source only requires you to specify the path. Now it works!

Outlook Unsafe Attachment Unlocker updated

 No Responses »
Mar 062007
 

Today I updated my Outlook Unsafe Attachment Unlocker utility. For some reason I noticed the select-all checkmark did not toggle. It only did a Select-All, but not an Unselect-All. Now it does. And the context-menu now points to the correct address of this weblog. Get it here.

Click to enlarge

When I get my hands on an Office 2007, I’ll see whether the utility can be made Office 2007 compatible.

Outlook Unsafe Attachments Unblocker

 No Responses »
Apr 122005
 

I still get a lot of search hits from people looking for a way to change the extensions that cannot be viewed in Outlook, because Microsoft decided in all her wisdom to mark a lot of extensions as “unsafe”. In Outlook Express there is a nice dialog to change this behaviour, in Outlook there is not. You can do it by editing the registry by hand, but a lot of people are afraid to do so.

For that reason, I created ouau.exe, or “Outlook Unsafe Attachments Unblocker”. It detects your Office version (which you can override) and lists the extension so you can block/unblock them. There’s a handy “select all” radiobutton that will save you some clicking.

Here is a screenshot.

Click here to download the program. It’s in WinRAR format, so you need to extract it first.

OUAU 1.1.0.0

 No Responses »
Apr 202004
 

OUAU should now work for all Office versions, and you can select the Office version (if for some reason you have partial Office installations) and it will reread and write the appropriate registry-entry.

Changes

  • Ability to change Office version by using the radiobuttons
  • Added link to this blog in context-menu

To do

  • Close the application when unsupported Office version is detected (detection and errormessage is already in place)

ouau has no effect?!

 No Responses »
Apr 202004
 

I tried ouau here at work, and we’re using Office 2002/XP. It finds the correct Office version, I’m able to make changes to the blocked extensions, which I can verify by restarting the program: it finds the new settings. But the new registry-setting resort no effect: right-click and send-to-mail-recipient of a unblocked extension (e.g. .EXE) still results in Outlook saying that the attachments are potentially unsafe. What’s going on here? Something to do with (group)policies?

Update: I think I already know: Exchange administrators can add/remove Level 1 and/or Level 2 extensions within the Exchange-server settings. This can not be overruled by the Outlookclient. So, I guess I’ll have to find another way to test other Office versions.

OUAU 1.0.5.0

 1 Response »
Apr 182004
 

Another update to OUAU, now version 1.0.5.0.

Changes:

  • Detection of Office 2000
  • Detection of Office 2002/XP
  • Detection of Office 2003

To do:

  • When user selects an Office version other than detected, modify the correct registry-entries, instead of detected version
  • Close the application when unsupported Office version is detected (detection and errormessage is already in place)

OUAU 1.0.4.0

 No Responses »
Apr 182004
 

Minor update to ouau, bringing it to version 1.0.4.0.

Changes:

  • All extensions show a description as tooltip when hovering the extension
  • When “Select all” is checked and an extension is unchecked, “Select all” will be unchecked as well
  • New Icon

Beperking ouau

 No Responses »
Apr 162004
 

Tim heeft ouau getest, en zegt dat het niet werkt. Hij heeft Office 2002 (XP). In TweakXP is wel te zien dat alle extensies zijn vrijgegeven. Klopt helemaal Tim, ouau werkt op dit moment alleen maar met Office 2003 (interne versie 11.0). Ik zal zo snel mogelijk zorgen dat alle Office versies vanaf 2000 werken.

 Older Entries  Newer Entries