|
-
Feb 14th, 2006, 09:07 AM
#1
Thread Starter
Don't Panic!
[Access 2003] Automation to Excel - tabs etc.
Hi,
Access 2003. Excel 2003.
My colleague has designed a neat looking form using a tab control and other controls in it. Looks great.
However, when he put an after update (or any other event) on one of those controls VBA errored with a very long message.
I suggested removing the reference to Excel and it ran fine. Put the reference back in the error returns (something like VBA cannot cope with the ole object (after update event)).
Has anyone else come across this?
Or do we just change the code to be objects instead of using the reference to Excel?
What a Day!

EDIT:
Okay its dissappeared. They were messing with it and now it works fine (freaky!) anyway, if you happen to come across this and can tell us what to do/not to do next time
Last edited by Ecniv; Feb 14th, 2006 at 09:37 AM.
Reason: Updating situation
Feeling like a fly on the inside of a closed window (Thunk!)
If I post a lot, it is because I am bored at work! ;D Or stuck...
* Anything I post can be only my opinion. Advice etc is up to you to persue...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|