|
-
Sep 12th, 2000, 03:45 AM
#4
Lively Member
to be honest I don't know, and would have to run the code to find out. As I said in my last post, try to isolate where the error is occuring. put some extra lines of code in like
Debug.Print 1
.
. some lines of existing code
.
Debug.Print 2
.
. some more existing code
.
Debug.Print 3
when it crashes see which was the last number to be printed, you will find the error after that print statement and before the next one
I relise that it is not theanswer you want, but it should help you to find the error
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
|