Printer-Object again
in [Visual Studio]
|
Prev: EjectNtmsMedia
Next: MSCOMM and Binary
From: Mike Williams on 10 Aug 2006 10:19 "Helge Haensel" <dj1wm(a)nurfuerspam.de> wrote in message news:op.td19iqqrsjedh2(a)hhh... > Did it. You are right. I will try to fix my problem with the > PDF995-driver now. I probably will have to make a system > restore. I will come up with an other post when i fixed the > driver and other problems still need help. So let us break this > thread here. Yep. Okay. The thread was getting way too long anyway, but I do like to keep threads going (and within the group) until the whatever Visual Basic problem you are having has been sorted out, partly becaue others might be interested and partly because all this stuff gets archived on Google and many threads are useful to other people for a long time into the future. By the way, when you do post back (if you do) it would be best to start a new thread. > Thank you for providing the code and of course your > detailed help instructions and advices. You're very welcome. By the way, I hope you were not shouting at me with that text in your last emssage that was in block capitals? The point I was trying to make, which was a very valid point, was that the Visual Basic problems you were having had been sorted out (one problem was sorted with the code I posted and the other problem was sorted with the service pack). I do know that you still do have a problem, but I wanted to point out that it is not a Visual Basic problem, and that it is in fact a problem with your PDF995 driver or something associated with it. Cheers Mike Williams (MVP - Visual Basic)
From: Helge Haensel on 10 Aug 2006 11:12
Am 10.08.2006, 16:19 Uhr, schrieb Mike Williams <mike(a)WhiskyAndCoke.com>: > "Helge Haensel" <dj1wm(a)nurfuerspam.de> wrote in message > news:op.td19iqqrsjedh2(a)hhh... > >> Did it. You are right. I will try to fix my problem with the >> PDF995-driver now. I probably will have to make a system >> restore. I will come up with an other post when i fixed the >> driver and other problems still need help. So let us break this >> thread here. > > Yep. Okay. The thread was getting way too long anyway, but I do like to > keep > threads going (and within the group) until the whatever Visual Basic > problem > you are having has been sorted out, partly becaue others might be > interested > and partly because all this stuff gets archived on Google and many > threads > are useful to other people for a long time into the future. By the way, > when > you do post back (if you do) it would be best to start a new thread. Some quickies here: I will post back here or in a new thread, sure. > >> Thank you for providing the code and of course your >> detailed help instructions and advices. > > You're very welcome. By the way, I hope you were not shouting at me with > that text in your last emssage that was in block capitals? The point I > was No, of course not. That msg was directed to myself because *I* saw possible problems with my system. It was only informative for others. Just a big uups or whatever! > with thetrying to make, which was a very valid point, was that the > Visual Basic > problems you were having had been sorted out (one problem was sorted with > the code I posted and the other problem was sorted with the service > pack). I > do know that you still do have a problem, but I wanted to point out that > it > is not a Visual Basic problem, and that it is in fact a problem with your > PDF995 driver or something associated with it. Well, allready nearly solved. I did not dl the PDFconvert package from PDF995. Excel and word print their PDF's allready again. A follow up will come soon in 'Printer.Object - great final', hi. Helge > > Cheers > > Mike Williams (MVP - Visual Basic) > |