Runtime error 340 Form_Load event

I have a program on my PC written in VB6 (MySQL database) that works when I run it here.  I used INNO SETUP for deployment.  The first form that pops up is a Login Form.  For one of the users, the following error appears after she hits the Login button.

       runtime error '340'
       control array element '1' doesnt exit
       Form = frmMain    Event = Form_Load

All other users can log into the system with no problems.  I uninstalled the program and reinstalled it and now all Userid's work.  Should I be concerned that this might happen again?  How would I best go about debugging issues on a User's system, as I could not recreate the error on my system?
LVL 1
inkineuAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hitesh ManglaniCommented:
the best way i guess is to use error handlers in every sub routine, in the error handler open a text file at a particular location and then log the important parameters and the error message. This will help you in getting the error without the need to recreate it.
0
inkineuAuthor Commented:
I do use error handles, ON ERROR GOTO ... , but that would not give me the line where the problem occured.  Is there a way to pickup the line?  My error routines display a message with the Subroutine name, error code and description.  Thanks
0
kevinfiggCommented:
When an activex control is regstered by an installer, this is (optionally) applied to all users in the All Users registry hive or local machine. Some installers will register it only to the user who is installing it.  In this case, I would suspect there was an issue with the user's profile.

I wouldn't worry about this too much, it might happen again - but then this is just normal run of the mill
problems installer apps have to deal with.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.