Ahhhhhhhhhhhhhhhhhhh!!!!!!!

Well that's the way the ball rolls

 

Today sucks. I don't even feel like posting.

 

No we yelled at the lady this morning and told her where she could stuff the 48 meg PDF file that did it. I mean who's ever heard of a 48 meg pdf file in the first place?

 

Do you hear it coming...

 

The macros I run are vast and mysterious. The people that wrote them are no longer with the company so we don't even fully understand what they do until they break and I have to reverse enginer them to find the problem.

Well one thing the macros do is look at the actual files they will link to and get some info from them like the file size. That way the file size shows up next to the link and you know how big it is before you try and view it.

Well the bone heads that wrote it put a cap on the file size a pdf could be and they set it to 32,657k (31 megs or so). It's proably a random number that they just threw in there becuase a PDF should never get that big even if it an 817 page manual for a product we stopped making 10 years ago.

What they forgot to do was to tell the macro what to do if the file was too big. I think this is the hidden part of the code....

Code:

If IsNull(ProdDocList.[BDPDF file size]) Then
            pdfsize = 0
        Else
            pdfsize = ProdDocList.[BDPDF file size]
If IsTooFriggenBig(ProdDocList.[BDPDF file size]) Then
            screwDane= crash

 

Well the good news is that i got it all fixed and was able to finish yesterdays work at about 2:30. Then i got to do todays work, and I get to sit and wait for the macros to run again.

Can you say "Never going home?"

 

I fail to see the humor in any of this

 

This isn't funny this is serious.

*evil music*

You can't stop me....

You wont know when it happens....

 

When what happens?

 

Your such a cute little doggie. Here here boy

 

I just want to go home, but i still have 2 more macro's to go