Printable View
I have a program that prints RTF files, and it works fine on any computer that has VB installed, but on computers that don't have VB installed, VB5 reports unexpected error while VB6 reports the Richtx32.ocx is out of date (which it is not).
The program reads in a file and dumps it into a rich text box and prints it out through it. Any suggestions? I tried copying all the resource files that are needed into the application directory but nothing worked. :(
Francis.
How do you know the RichTextBox OCX is NOT out of date????
I would suggest including this OCX in your distribution of the application so that the end user gets the same version that you are using.
VB is one of those languages that requires a lot of support files to get applications to run on machines without the language... its just a fact of life.
Thanks for you response, but I just found the answer and it's an interesting one. Richtx32.ocx isn't out of date for sure, because I just installed VB6 with SP3, which is the newest version. It's just giving me some BS.
The real reason why computers with VB can run the program is because when VB is installed it registers all the VB OCXs in the computer's registry, so if it ain't registered, then it claims I have an old version. After I registered both OCXs all the computers I tested it on worked.
Well, you learn something new everyday. :)
Francis.
If you include the ocx in your distribution, then it should automatically get registered on the end user pcs.
Paylo, you are not 'Distributing' your application, but just copying the required files manually! This is in violation of the law we all have agreed upon when we started programming with VB!
You will receive due punishment for this crime and from now on, your mailbox will be flooded with junk mail that explains how to use the Package & Deployment Wizard with VB5 or VB6.
Remember, whenever you create an application in VB, you have to create a distributable/installable copy of it. Once such a copy has been created, it contains a file Setup.exe which installs (not just copy) your app on the client machine. In future, always use the Package and Deployment wizard to create a distributable copy of your app.
First of all, it's not an application in the sense that it does alot! It's a command line program that simply prints rtf files from command prompt. I don't see why that needs a "setup" program. So if I send out a little hellow world program I need to setup that too?
[Edited by Paylo on 08-01-2000 at 03:41 AM]
Yeah that's the bi**hin' part of vb. The comp that you want to run it on HAS to have the proper dll's and runtime files.
Laterz,
D!m
Anyone have a better way of printing an RTF without a richtext box? :) (or common dialog box for that matter)
I would have suggested printing from a normal textbox but it's not as flexible as the richtextbox. I would stick with the richtextbox, but if you really want to...
See if this helps you:
http://www.planetsourcecode.com/vb/s...txtCodeId=8167
Laterz,
D!m
Thanks for the help, but I think RTF is the way to go since normal text can't print out tables (sigh, another requirement in the program)
BTW, does it really say in copyright I can't distribute libraries??? That sounds ridicolous, since you can run a program with a library if you don't have the program, and technically I bought the rights to the library.
I understand Setup is great for big apps, but these small little helper functions shouldn't need to be under such a restrictions. After all, there are some dlls and ocxs that are always in some programs, (there are 4 basic ones I think?) and nobody ever complains when you distribute those.
Ah well...
Francis.
That does sound wierd, i don't think that's right b/c when you buy vb, you buy the license to those libraries (i think, i hope) :)Quote:
does it really say in copyright I can't distribute libraries???
Laterz,
D!m
It doesn't matter how small or simple your app is, you still have to use the setup option to get it to work on an end user machine.
What's this about not being able to distribute library functions. You can distribute any ot the dlls and ocxs you need to run your program.However if third party check that they can also be freely distributed, normally this is the case
However if third party check that they can also be freely distributed, normally this is the case
What do you mean by third party check?
And, you can't use the setup program if it's not a stand alone application. (In a very real sense, it's not an application, it's supporting function)
The rest of the program might not be in VB, then whaddaya do?
Third Party Controls - check the licencing agreement to ensure free distribution with your apps.
Ok if part of app is vb part is something else. You still need to distribute the vb part with all dlls ocxs etc to ensure the vb part is going to work as planned.
Yup, that was what I was doing b4. You thought differently? :)
We have a couple of utilities that don't even have forms, just modules...and we still need to use the Distribution option.
Just one part of dll hell, don't even get me started on the worst aspect of this.
But I just want to clarify, you are using the distribution package because it's more convenient or for copyright reasons?
Paylo, I think it works like this:
You have an application which uses certain DLL files. Now your application also has to know where these files are located and such other stuff.
For VB applications, these applications take the help of the Windows registry to locate the various DLL files required by them.
For C++, I think the path of the files is used directly. So there is no need to access the registry.
Since the VB applications access the registry for DLL information, all DLL files needed by a VB app need to be registered. The P&DW does exactly that. Whatever DLL, OCX and other files are required by your VB application are bundled together in the distribution package, and code is written by the wizard to copy them onto the target machine and make an entry for each of them in the registry. It is not compulsory that you use the P&DW, but then you will have to manually register each of the files, which is not possible.
Ok.... so the conclusion is..... it's not illegal!!! :0
Yes I knew you could do it both ways, but sometimes it's better to not use the wizard.
that answers the question. Thank you.
1. Need to build all required dlls/ocxs into one setup set of disks.
2. Still evaluating Wise etc third party distribution systems.
It is not illegal to distribute the required files to run an application on another machine. That's the whole point of desk top development else we would all be using delphi or something similar.This is not illegal
Sone third party controls require a license to include them in deployments, we keep well clear of these turkeys. Most suppliers will say somewhere in their documentation that the control can be freely distributed with your app.
When you generate your distribution files, the process picks up all required dlls etc, you have to add any databases, images etc.