< Back to OSY 1.0 thread list

OSY 1.0 Thread Viewer

Thread #: 1222

Win 98 errors return...

Madan

Tue Dec 4 01:00:18 2001

excel?

errrrrrr......


excel is rough? *sigh*


:rolleyes:

M.

(Edited by Madan at 5:00 pm on Dec. 3, 2001)

(Edited by Madan at 5:01 pm on Dec. 3, 2001)

pauli

Tue Dec 4 04:51:44 2001

now THAT is an ulgy color scheme!

(though it's still better than horizontal stripes)

AllYorBaseRBelong2Us

Tue Dec 4 05:55:04 2001

That is indeed wretchid.
DuffMan

Tue Dec 4 11:56:12 2001

Huh? Where's the error? All I see is a VB runtime error, most likely caused by a problem in a macro in the spread sheet. Why would you blame Excel for the spreadsheet creator's mistake?
Harbinger

Tue Dec 4 14:29:17 2001

from DuffMan posted at 6:56 am on Dec. 4, 2001

Huh? Where's the error? All I see is a VB runtime error, most likely caused by a problem in a macro in the spread sheet. Why would you blame Excel for the spreadsheet creator's mistake?

Yeah, I don't quite see where the "Win 98 error" is.

OscarWilde

Tue Dec 4 16:46:00 2001

To a mac user, any un-elegant dialog box is an error...

;)

HitScan

Tue Dec 4 17:17:56 2001

OW: Perhaps this is a more appropriate error message:

"For let it go down in the course of human events that on this day the program known amongst its friends as Visual Basic has detected an error numbering '5' amidst the throes of its functioning. The moniker of this heinous error is "Invalid procedure call or argument" And lo, thou must restart thine computer for the full effect of this syntactical perversion to be assuaged."

Any more "elegant" and I'd have to put a shortcut to dictionary.com on my desktop ;)

(Edited by HitScan at 9:18 am on Dec. 4, 2001)

Madan

Tue Dec 4 20:39:35 2001

You guys don't *get* it.

Huh? Where's the error? All I see is a VB runtime error, most likely caused by a problem in a macro in the spread sheet. Why would you blame Excel for the spreadsheet creator's mistake?

Yes. I wasn't, to my knowledge *using* macros.

Mad.

Magus

Tue Dec 4 21:31:20 2001

Maybe you'd like an error message like this?

First shalt the spreadsheet err. Then shalt Excel number the error 5. No more, no less, and the number of the error shall be 5. 3 shall it not count, nor count it 4, except that it then proceed to 5. 6 is right out! When the error is numbered 5, being the 5th error being numbered, then lobbest thou thy Holy MessageBox of Visual Basic towards thy user who, being naughty for using macros, shall be dismayed.

Better? :)

postCount++;

Madan

Tue Dec 4 22:00:02 2001

Pauli,

A. There *is* no "color scheme".
B. Windows is ugly to the bone.
C. I just used one of the themes included in 98--white.
D. It's hella easy to read. Why else would books all have.......

*drumbroll*

*WHITE* pages. :boggle:...

Mad.

Madan

Tue Dec 4 22:03:13 2001

*Sigh*...

Let's try this again...

I made the excel sheet. I didn't(to my knowledge) use macros.

Is a macro a simple multiplication command on one column? Is it coloring one bar yellow or underlining the bar?

If not, then I didn't *use* macros.

Mad.

OscarWilde

Wed Dec 5 04:18:04 2001

No you might have macros enabled by default. Granted if you are not using macros you shouldn't get a macro error. But who ever said that anything from microsoft should work with reason? Besides I'm extremely sure that Microsoft got into your computer hid some macros in your excel file which wouldn't work. Then when you get the error you would be compelled to run out and Get Windows and Office XP, for a completely whole new eXPerience.

Pretty darn sly aren't they?

Hitscan, Magus, bloody funny stuff. I would compete and type up something funny too, but you guys pretty much did it all.
Ha ha ha!! that has to be two of the funniest post on OSY for a long time.

Magus you are learning fast grasshopper. You might one day be amongst the ranks of which greatness is the domain. I await what is your destiny.

DuffMan

Wed Dec 5 12:33:08 2001

That's strange. What happened after the error ocurred?
HitScan

Wed Dec 5 14:12:07 2001


Hitscan, Magus, bloody funny stuff. I would compete and type up something funny too, but you guys pretty much did it all.
Ha ha ha!! that has to be two of the funniest post on OSY for a long time.

We appreciate the compliments our poopy-headed leige. ;)
That's the most work I think I've put into a post in weeks. Since the last bitch-fest I've had anyway, heh.
Madan

Wed Dec 5 20:34:23 2001

No you might have macros enabled by default. Granted if you are not using macros you shouldn't get a macro error.

Hmm. I *think* that would be my POINT. And no, my macros aren't on.

I tried to kill the app. after a print job and it gave me that horror.

But who ever said that anything from microsoft should work with reason? Besides I'm extremely sure that Microsoft got into your computer hid some macros in your excel file which wouldn't work. Then when you get the error you would be compelled to run out and Get Windows and Office XP, for a completely whole new eXPerience.

Actually, it's the negligence that smokes me.

M.