asked on

Slightly Odd Behavior

Hello.

This is rather a difficult question to ask. Basically we have an application we created. With this application it asks for a user id and password, the script confirms it and then opens a form. All this works wonderful on all machines.

Then one day we decide to add some code deeper in the program. Now on two machines it asks for the user id and password and just hangs. On all other machines it works fine. We did not touch the code that has to do with the log on.

The program was written in VB 6.0 and is run on NT workstations without VB installed. As I said, it worked fine until this change was made.

We have reinstalled the application still to no avail. Does anybody at all have any ideas?

I know this one is difficult.

Thanks,

nnaxor

ASKER CERTIFIED SOLUTION

Guy Hengel [angelIII / a3]

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Julian_K

Well... remove all "On Error" statements and check where it hangs ;-)

I suggest you writing a small DLL for run-time logging.
The easiest way is to open a text file and in the beginning of each procedure/function to write to this file the name (eventually the parameters).
When the program hangs, you can view the text file and get more info on where exactly it hangs, and what parameters were recieved, etc. It's not a lot of work.

nnaxor

ASKER

That makes sense and seems like a good idea, however, the problem we have is that it only happens on two machines. The other dozen or so it works fine on. This would seem more like a machine related problem rather then the program. Unless I am missing something. Because it was working on those machines before. It is on a network drive and we actually install the app on those pcs. I'm not sure how debugging on a single machine will make any difference.

Julian_K

angelIII, you're faster :-)

Guy Hengel [angelIII / a3]

Debugging will SHOW you the difference you can't see right now. It will tell you in which procedure the code hangs -> you will only have few lines to read and try to imagine what the problem could be. Something HAS changed, you don't know -> You DEBUG !!!
CHeers

nnaxor

ASKER

nnaxor

ASKER

Sorry about the double post. You are both entirely correct. The machines that are not working are not close by and so before beginning the trek there I wanted to confirm there was nothing else it could be. As it seemed machine related. We will do as suggested as soon as we can get to those machines. Thanks much and let's hope this helps.

nnaxor

ASKER

BINGO - you guys so rule - no wonder it is called experts-exchange <grin>.

Okay now we get an error:

430 Class does not support Automation or does not support expected interface.

Angellll?

nnaxor

ASKER

Thanks much. As this helped to diagnois so we could find the problem, I will go ahead and close out this question and start another one now that I know what the problem is.

Guy Hengel [angelIII / a3]

Hi,
Glad we could help you by pushing you :-)

430: you probably have
* a binary installed that is not installed with the correct version

When you know on which line the error occurs, you know the class that it expects, and compare the version of the development PC with the one on the PC where the problem occurs.

CHeers