This would be easier, I understand, if the version of our software that I was trying to compile was being compiled with Visual Studio 2010 instead of Visual Studio 2005. But it isn't and so here I am ( Read more... )

I'm trying to debug our ADO connectivity to an Oracle database using the Oracle OLE DB drivers ( Read more... )

I have knocked off the bugs that were assigned to me for our upcoming patch release and can now work on something that's more fun. :)

(Ok, I walked through a 17,000 line file today where the least problem that I fixed was unnecessary extra copying of assorted BSTRs of possibly great length; others of the BSTRs were being leaked, because no one ( Read more... )

daisy_knotwise is on her second day of antibiotics and is feeling much better ( Read more... )

This is possibly because I'm coming down with the strep infection that daisy_knotwise just got diagnosed today. (And she now has antibiotics. If my throat is sore tomorrow, I'll be looking for some myself.)

But the more likely cause of my headache is that I have, I think, figured out the multiple sources of our massive memory leaks.

Every call that we made ( Read more... )

The problem with coming to a project at a later stage of development is that a number of design decisions will have been made for you. Right now, I'm discovering that some of them seem to be fairly marginal ( Read more... )

It appears that we have a big memory leak in our application. Some of it is my fault, because I copied incorrectly working code without bothering to check how a particular class worked.

Short form: our COM routines return a BSTR. If you assign that BSTR value to an object of the CComBSTR class, the value is copied to the internal storage for ( Read more... )

I spent much of the weekend and this morning beating ClearCase into submission on the VM. Having gotten that done, I was able to get started on my next (small, I hope) project, which is reworking our ADO COM code to use smart pointers. With a reasonable amount of luck, this will solve some of our memory issues ( Read more... )

You have to understand that I receive a pretty fair number of bogus bug reports. So I got a report that said that our new client app that we're busy testing for the next release would shut down when you opened the Save As dialog and changed the file type. I was naturally skeptical and I couldn't duplicate the problem, but we had a number of ( Read more... )

So I have been condemned to support a testing web page that someone else wrote long ago and that we have done a lousy job of maintaining. One of the things that the testing web page does is to check out a file from our file server, write it to a local directory, then check the file back in, and finally delete it from the local directory ( Read more... )