Link to home
Start Free TrialLog in
Avatar of jnri
jnri

asked on

16 bit visual basic version 4 problem

Hello,

I support an old software product that resides on a windows 98 computer.
This application is written in VB4 16 bit version.  The program all of a sudden (my clients swear they did nothing to the computer) started working incorrectly.  The problem is that when the program is run the icon appears in the task bar but the window does not show up on the screen.  If you click on the taskbar icon it does not open up on top.  The program doesn't seem to work correctly and I can't figure out why.

I have reloaded VB4 and have re-booted the program. No change.  I re-compiled the code into a new executable and it had no affect.

I have run into this problem twice before (the same program runs in 4 different facilities) and reloading VB and/or recompiling has solved the problem.  

I am assuming there is some old DLL or 16 bit way of doing things that is getting stepped on by some newer software but I do not know enough about what is going on to be able to solve this myself.

Any ideas would be greatly appreciated.  

Thanks

John
ASKER CERTIFIED SOLUTION
Avatar of JCinDE
JCinDE

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Or right click on toolbar and choose cascade window when you app is opened
Avatar of jnri
jnri

ASKER

Thanks.. the move thing seemed to work. Any ideas why this would happen?.. Not important just curious.


Could be that whereever the window position is stored, that file got corrupted somehow. Or perhaps someone change the screen resolution to a higher setting, ran the program and then changed the screen resolution back.

Most likely, though, it happened because the program exited when it was minimized and it wasn't written to handle that gracefully. Tell them not to shut down the computer when the program is running (especially if it's minimized) and not to close the program by right-clicking the task button when it's minimized.

At any rate, you know how to fix it if it happens again.