Question : VB6 end of support - consequences for practice

Hello,

I have read that the extended support for Microsoft VB6 ended at March 2008.
From the Microsoft page I know, that Microsoft stopped delivering service packs for VB6. My question is: what are the practical consequences for following scenario?

There is a maintenance contract for an old VB6 application, which is running very stable and nearly without any bugs since many years. There may be occure some smaller bugs in the future, but not very probably. And there may be some wishes for smaller enhancements. Until now no bigger changes are planned.
(The application is used in the finances environment, administrates real money accounts and connects to the internet to get realtime finance data).

Is it irresponsible to use the application (a migration to .NET / redevelopment is vital) ?
Or, can (with a clear conscience) recommend to use the application "as it is" because the practicel risks are negligible.

I know it may be not really possible to make a final statement, because future problems with VB6 (which would require a service pack) can not be foreseen. but what would be your strategy/ recommondation, resp. how would be your approach for a risk assessment.

Best regards an many thanks in advance for your input.

Hattl

Answer : VB6 end of support - consequences for practice

>what are the [u]practical [/u]consequences for following scenario?
close to none. we are still using VB6 quite a lot. "known issues"  are known, and for most, a workaround is possible/known.

>Is it irresponsible to use the application (a migration to .NET / redevelopment is vital) ?
no. I have an application developed in 1996 (VB5 initally, moved shortly after to VB6) still running as of today!