Anyone had this before?? VB

Posted by Ian on August 01, 2001 9:07 AM

I have lots of people using excel and userforms I've set up. I'll try and go over everything.

All the files came from a single template, which was then Saved As each_persons_name.xls

they open the files from a shortcut on the desktop, this is the only way they can get excel to come up (security reasons).

when they Enable Macros (If more like) the form open via the Workbook_open event.

The forms have the X box removed so they can't just exit.

they then do there stuff, pushing buttons and what not. After which a Submit button Saves the file, dumps the info inputed on to a sheet and re loads the form.

at the end of the day they End Session and the book saves and excel quits.

Phew!! all that for 2 tiny questions.

1 person is getting Dr.Watson reports all the time
and 1 persons Excel hangs on the Save part of Submit??

they use a generic log-in winNT, they have moved seats (they have even just today move floors!!) and both of these things still happen every time. I've had a word with IT and because of the generic Log-In it IS NOT a profile thing.

Excel 97 is what they use

Thanks are due to the person who sheds light on this baby.

Ian

Posted by Jerid on August 01, 2001 10:36 AM

Thats a difficult one with out seeing it.

Maybe this will help, I have seen Dr. Watson errors in Excel97 for the following reasons.

1) VB code runtime error, instead of giving me a VB error, somtimes I get a GPF.
2) Code surrounding Addins, we use the Hyperion EssBase addin, and I get GPF's with it sometimes.
3) A corrupt control on a form (eg. Command Button, TextBox etc..)

Sorry, not much help.

Jerid

Posted by Ian on August 02, 2001 1:23 AM

Aparently the hanging thin is happening to a few people now, and not all the time.

anyhting I could look for. I have gone with this form before and not had any problems.

Ian

Posted by Jerid on August 02, 2001 5:18 AM

You need to find something in common with all of the GPF's and hangs.

With these kind of problems, I usually keep myself a log, when the user has a problem I ask them what they were doing when it happened and then write it down until I can see a pattern.
Most of the time you need to train them to pay attention to what they were doing.

Once you narrow down where the problem is coming from, then you should be able to fix it.

Can you give a sample of the code in your summit button?

Jerid