M
Montana DOJ Help Desk
I just wanted to take a moment to thank all those in this group that have
helped me out over the last year or so. I've asked a number of questions
and always received excellent help. The project that I've been working on
is finally completed.
In the course of doing this project, I worked with many elements to Word and
VBA for the first. Manipulating the contents of the clipboard, working with
collections (both built-in and custom collections), range objects,
user-defined data types, and the Err object, writing data to files, reading
data from files, using KeyDown events, and a whole host of other things to
numerous to mention, where all firsts for me.
I also had a lot of fun experiences (and by that I mean absolutely
maddening). I got to learn first hand about the "Project unviewable"
message, and found that I needed to use a code cleaner to eliminate the
bloat in my project. The only problem was that I kept getting an error when
I tried to run code cleaner. By removing user forms one at a time and
running the code cleaner, I eventually traced the error to a particular user
form, and by removing items on that form one at a time and running the code
cleaner, I eventually traced the problem to a single label on that form.
Wheee! That was FUN!
Prior to this project I had worked a little bit with error trapping, but not
too much because most of my previous projects had been so small that it
wasn't really worth the effort. This project, however, was fairly large and
I had to immerse myself in the finer points of error handling for the first
time. I did a pretty good job too, if I don't say so myself. If the
programming can't handle an error by itself, it displays the data to the
user and gives the user the choice of keeping or discarding the data. Every
error is logged, and I've provided two toolbar buttons--one which allows to
open the error log in another window, and another which brings up a user
form that allows the user to page back and forth between records in the
error log and to open the Help file for each error by clicking a Lookup
Error button.
I tested this programming to death, but even so I ran into an error just
last night that I had never thought about. One routine feeds the contents
of the clipboard into a string variable. I had considered what happens when
nothing is on the clipboard, but never considered that the clipboard might
contain an object, such as a file or folder. My error trapping routines
actually handled the error exactly as designed, which made me feel pretty
good.
I could not have completed this project without the excellent help of people
in this group. I just wanted to take a moment to thank everyone who has
offered help, and to let you know that your efforts enabled me to
successfully conclude this project.
Thanks again!
-- Tom
State of Montana
Department of Justice Help Desk
"Making the world a safer place."
helped me out over the last year or so. I've asked a number of questions
and always received excellent help. The project that I've been working on
is finally completed.
In the course of doing this project, I worked with many elements to Word and
VBA for the first. Manipulating the contents of the clipboard, working with
collections (both built-in and custom collections), range objects,
user-defined data types, and the Err object, writing data to files, reading
data from files, using KeyDown events, and a whole host of other things to
numerous to mention, where all firsts for me.
I also had a lot of fun experiences (and by that I mean absolutely
maddening). I got to learn first hand about the "Project unviewable"
message, and found that I needed to use a code cleaner to eliminate the
bloat in my project. The only problem was that I kept getting an error when
I tried to run code cleaner. By removing user forms one at a time and
running the code cleaner, I eventually traced the error to a particular user
form, and by removing items on that form one at a time and running the code
cleaner, I eventually traced the problem to a single label on that form.
Wheee! That was FUN!
Prior to this project I had worked a little bit with error trapping, but not
too much because most of my previous projects had been so small that it
wasn't really worth the effort. This project, however, was fairly large and
I had to immerse myself in the finer points of error handling for the first
time. I did a pretty good job too, if I don't say so myself. If the
programming can't handle an error by itself, it displays the data to the
user and gives the user the choice of keeping or discarding the data. Every
error is logged, and I've provided two toolbar buttons--one which allows to
open the error log in another window, and another which brings up a user
form that allows the user to page back and forth between records in the
error log and to open the Help file for each error by clicking a Lookup
Error button.
I tested this programming to death, but even so I ran into an error just
last night that I had never thought about. One routine feeds the contents
of the clipboard into a string variable. I had considered what happens when
nothing is on the clipboard, but never considered that the clipboard might
contain an object, such as a file or folder. My error trapping routines
actually handled the error exactly as designed, which made me feel pretty
good.
I could not have completed this project without the excellent help of people
in this group. I just wanted to take a moment to thank everyone who has
offered help, and to let you know that your efforts enabled me to
successfully conclude this project.
Thanks again!
-- Tom
State of Montana
Department of Justice Help Desk
"Making the world a safer place."
