I've lately been finding that some of my VB6 customers are experiencing odd crashes around calls to SQL stored procedures. Getting what appears on the surface to be a timeout on the client side when in reality the SPROC runs instantly in QA. Now I'm a database programmer for 30 years and I know how to debug problems. I've not gotten to the bottom of this one yet - and I'm starting to suspect that ADO is not keeping up with how the server-side is processing requests.

The only lucky thing going for me is that I have a migration plan that I started three years ago that I can use to re-build these screens or interfaces. Plan is to leave the VB6 stuff behind ASAP.

If I had a modern VB6 replacement IDE that ran in all new versions of WINDOWS - that would accept the SOURCE and PROJECT files from this VB6 app - I would have possibly changed my migration strategies.

Although part of the strategy has to involve your customers. Do they still want a VB6-only user-interface? From my customers I am able to get funds for the migration - it might be multi-year with some - might not be full development costs for others. Regardless, as an ISV I have always thought of myself as a professional like an architect or lawyer. Some hours you work are fully compensated for - others are support and maintenance - some pro bono.

What are the two applications that you make a living with actually do? Do they involves MS SQL-like databases?