|T O P I C R E V I E W
||Posted - 01/15/2008 : 01:04:54
I have implemented your control in one of my customer applications I have developed, using VB6.
I compile the program, and the executable runs just fine,
Now I am running it on Windows Vista, and it runs OK,
but when I shut the program down, Vista produces an Error message,
and tells me it is attempting to find a solution,
and asks if I want to Debug the program.
Of course, I CAN'T have this scenario for my users.
When I use your object in Development mode, everything works just fine;
it is only after the program is compiled into an .exe that this occurs.
Note that it does NOT happen in XP.
I have proven this by using your example to create some rotated text, and complied it into an .exe.
Running in WindowsXP, it completes fine;
but running in Vista, when closing the program I get a box which says "program has stopped working", and tells me about putting info into a temp file.... here is the contents of that file
Windows NT Version 6.0 Build: 6000
Product (0x1): Windows Vista (TM) Ultimate
Flavor: Multiprocessor Free
HELP !!!!!!! High Priority !!!!!!
|13 L A T E S T R E P L I E S (Newest First)
||Posted - 08/03/2017 : 13:12:23
It's still no solve for this kind of problem ... error happened when app EXE shutted-down under Windows 7 Operating System
||Posted - 12/17/2012 : 14:11:09
I have the same problem on my windows 7 installation. Seems that the error comes when the form that contains the preview dll is in unload state - in my case i tried with and without a 'Set preview=Nothing' on Form_Unload in my VB6 project.
Have i anything missing to cleanup the preview dll before unloading?
||Posted - 11/25/2008 : 17:42:34
I have been thinking some more about the situation and if the developers have given up then that should release the source code to allow others to take over the work. After all the developers have taken our money made their profit and gone without a word. I would not have minded paying again for the component if it works correctly with Vista.
||Posted - 11/25/2008 : 16:40:11
Yes I think itís very poor that we have been left stranded with a product which does not work and no help to sort it out. I think the developers should remove this component from sale or at least give a very strong warring.
From what I can see you cannot get support and there is no development work. Itís a shame as is a very good component.
I would be interested in a new print component for my legacy software.
||Posted - 11/12/2008 : 04:08:50
I have built my own version of a Print Preview, which does not die under Vista.
If anyone is interested, visit this site www.qdog-software.com
||Posted - 05/23/2008 : 19:22:11
I have come to the conclusion that Waty has no interest or intention
of solving this issue. Nor does he have any thoughts to respond to us
in this forum.
I am undertaking to create my own Print Preview from scratch.
I am about 50% done with the fundamentals, and am now trying to resolve
some of the esoteric things I have run into.
If anyone would like to help/contribute/whatever to this project,
I would be most happy to hear from you.
||Posted - 05/02/2008 : 06:25:44
I agree with you. I have had a problem since 2006 with the program, and watty never really fixed the program. At this point Ill sign ANY thing to get the source code, so I can fix the problem, so I can use the software.
Its very good application, but the support fails, and I have gotten into much trouble in the past using the buggy software.
Let me know if anything comes of this?
||Posted - 03/29/2008 : 20:56:22
Waty sent me another attempt, after working on it over the Easter Weekend.
Still no joy.
WBGookin, I agree.... I would LOVE to get a chance to help out, by looking at the code.
I am even willing to build my own version to do this...
not in an attempt to compete with Waty's, but merely to have a product that I can use in my application,
and which works with Vista.
My only "stumbling" block is the exporting to DOC, RTF, PDF, TXT file.
I can easily build the build/preview part. In fact, I have already done so.
Any thoughts on how to export to those files types I mentioned ?
Or does ANYONE have any thoughts on how to do it ?
If willing, I can give my email address so anyone else interested in this can communicate with me
outside this forum/site.
||Posted - 03/20/2008 : 15:49:22
Is it possible that it's not the ppreview.dll, but one of the supporting dlls (ijl11.dll, zlib.dll, etc) that's the problem? Maybe one of the I hate the problems that don't show up in the compiler, but do show up in exes.
I guess I have to now buy Vista to develop/test on. Yech.
I understand that fixing this is not Waty's focus, but if he has given up on the code, please let us take a look at fixing it...
||Posted - 03/19/2008 : 16:25:21
It seems (to me) that neither Waty or Mike visit this site....
if they do, it is only once in a "blue moon".
And it would also appear the Waty has no further interest in "fixing" this problem.
He is not replying to my Emails anymore
(I haven't' sent any more than about 8 or 10 over 2 months).
I asked him to let me have SOME of his source code, particularly where the control is first instantiated, but no response.
WBGookin also suggested that here.
I have been paid for my development work, providing MY client with a product which they, in turn, market and sell as a world-wide security assessment solution.
Now their clients are complaining loudly about this error message,
and, of course, my client is complaining LOUDLY to me.
I have done extensive research to find an alternative product, and there just isn't anything out there (except Crystal Reports) which will export a report to a RTF, PDF, DOC, TXT, etc. file.
All the experts regarding CR I have spoken to say my particular requirements and logic in creating the reports is far too complex for CR to handle it.
So I am caught between a rock and a hard place.
Come on Waty... LET'S GET THIS PROBLEM FIXED.
||Posted - 03/17/2008 : 01:55:28
OK, I have the problem too (I imagine everyone does). It would be GREATLY appreciated if a fix could be found for this...I really don't want to rewrite (again) my print routines.
I don't suppose you'd want to make the source available to us, eh? :)
||Posted - 03/17/2008 : 00:39:30
Can you just "on error resume next" the problem somehow? This could be HUGE for me as well, as I'm about to deploy a big update that now uses this control. (I have to find a vista machine to test on!)
||Posted - 03/15/2008 : 19:26:30
Well, Waty and I have made several emails back and forth.
I have sent him a sample VB6 simple program/code (no statements other than to declare his control) which has this situation happen.
He has agreed that he also is experiencing it happening with a few programs.
But he says he cannot figure out how to fix it.
So... can I have my money back ????? (actually I paid twice too)