Visual Basic, VB6.0 SP1 wiped out my Print method

VB6.0 SP1 wiped out my Print method

Author	Message
Andrew McCarte #1 / 5	VB6.0 SP1 wiped out my Print method I've just installed the SP1 for VB6.0 and I swear I've lost my Print method. If I create a form called frmPrint and call: frmPrint.Print "Boo Hoo" from another form, I now get a 438 Run Time error - method not supported. 1) This didn't happen before SP1 2) I don't even get the Print method as an option in the Intellisense window anymore - all I get is PrintForm. I checked out the 438 Run Time error article in the knowledge base where they tell you to edit the TabOrder.vbp file - I don't even have that file to edit. Has anyone else encountered this with SP1? Am I going to have to re-install Visual Studio?
Tue, 24 Apr 2001 03:00:00 GMT

Bob Schuett #2 / 5	VB6.0 SP1 wiped out my Print method OK Here, FormX.Print "Test". FormX.Picture1.Print "Test" A-OK FYI, Running a VB416/VB532 conditional compile project in VB6SP1 on NT4SP3. Man, if nothing else, Microsoft has really helped increase the amount of Jargon. Bob Quote: >I've just installed the SP1 for VB6.0 and I swear I've lost my Print method. >If I create a form called frmPrint and call: >frmPrint.Print "Boo Hoo" >from another form, I now get a 438 Run Time error - method not supported. >1) This didn't happen before SP1 >2) I don't even get the Print method as an option in the Intellisense window >anymore - all I get is PrintForm. >I checked out the 438 Run Time error article in the knowledge base where >they tell you to edit the TabOrder.vbp file - I don't even have that file to >edit. >Has anyone else encountered this with SP1? Am I going to have to re-install >Visual Studio?
Tue, 24 Apr 2001 03:00:00 GMT

Andrew McCarte #3 / 5	VB6.0 SP1 wiped out my Print method OK, now I'm REALLY confused! Maybe I'd better junk Windows 95 and do the NT thing - I've been looking for an excuse.
Tue, 24 Apr 2001 03:00:00 GMT

Bob Schuett #4 / 5	VB6.0 SP1 wiped out my Print method If you're serious, I suggest (1) using a seperate unit, or (2) putting in 2nd drive that you can plug / unplug for when you want 95 or NT, or (3) using a dual boot operating system. You may find NT not so satisfying, and certainly will find it harder to configure than 95. NT4 has no plug and play, and no hardware wizards. It looks and smells like 95/98, but the change will certainly slow you down in the intial stages while you get your system configured. Good luck, Bob Quote: >OK, now I'm REALLY confused! Maybe I'd better junk Windows 95 and do the NT >thing - I've been looking for an excuse.
Wed, 25 Apr 2001 03:00:00 GMT

Jonathan Alle #5 / 5	VB6.0 SP1 wiped out my Print method @cts.com X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Newsgroups: microsoft.public.vb.bugs A note on NT 4.0 If your BIOS has an option for Plug and Play aware OS, set it to False. I spent several hours fighting with NT Server over a network card before I stumbled across that trick. Afterwards it worked fine. Greywolf Ghost Quote: >If you're serious, I suggest (1) using a seperate unit, or (2) putting in >2nd drive that you can plug / unplug for when you want 95 or NT, or (3) >using a dual boot operating system. You may find NT not so satisfying, and >certainly will find it harder to configure than 95. NT4 has no plug and >play, and no hardware wizards. It looks and smells like 95/98, but the >change will certainly slow you down in the intial stages while you get your >system configured. >Good luck, >Bob >>OK, now I'm REALLY confused! Maybe I'd better junk Windows 95 and do the NT >>thing - I've been looking for an excuse.
Thu, 26 Apr 2001 03:00:00 GMT

Page 1 of 1

[ 5 post ]