Q:  I have used SQL procedure in my vb6 application. The application is client server, on some clients procedure runs fine. But on some clients, procedure does not run. It does not show any error - what should be done?

Kevin Kline says:  The answer to this problem might not be what you want to hear. In a nutshell, your problem illustrates that your VB6 application does not have enough internal logging.

You should add code to the application that allows you to enable a “Debug” mode that tells you everything that the application is doing. It may be possible that the error isn’t in SQL Server at all, but is in your VB6 application and is not properly invoking the stored procedures.

To further learn what’s happening from the SQL Server side of things, bring up SQL Profiler and trace the sessions that are working and also not working. You can then see all of the commands that are being sent to the SQL Server and correlate that activity to any failed stored procedure calls.

If you’re not familiar with SQL Profiler, read about it in the SQL Server Books On-Line. It’s well documented there.

Technorati Tags:
SQL Server, Visual Basic, logging, debugging, SQL profiler, books online
Add to: | Technorati | Digg | del.icio.us | Yahoo | reddit |