Printable View
I Want To Install My Program On One Computer (Server) AND Run My Program On the Other Computers on the Local Network Without Installing it On all computers . So What i should make in .OCX , DLL . I Know that it should be Registered on every computer to run the program . So What is the Solution ?
Note : I Can Run the application on all computers with installing it on every computer but i want to install it on the server only Like SQL Server
Many Thanks For All At First For Your Help
First... don't. Trust me. Just ... don't. It's a bad idea. SQL Server is a bad comparison because it never runs on the local system... it's a SERVICE... running on the server. It does not run on the local system at all. Now, the Management Studio does run locally, but the database and the server side stuff still actually run on the server.
When you run a VB6 app (unless things have changed) basically what has to happen is that a copy has to be retrieved locally so that it can be run... and that takes time. And ends up with a lot of network traffic going back and forth. Plus you have to install any components locally in the first place right? So why not just install the app on the machines in the first place?
-tg
Asume That I want To Run the application on one computer Only without installing it on the computer . what i must do to run the program ???
the program can be run on any computer networked to the server. that being said, if the network computers don't have the .dll files required to run either a simple vb app (msvbvm60.dll) or any .ocx/.dll files your app requires, you will receive an error message stating those files cannot be found.
VB6 does not have a compiler option to produce compiled output marked for running from a network file share. The libraries included with VB6 are not marked this way either, and almost no 3rd party libraries are.
This "mark" tells Windows to load the entire file into memory and keep it there for the duration of a run. The reason is that the EXE, DLL, etc. does not simply get read once but instead parts get read and reread during the life of a run due to overlay activity (system virtual memory management).
Very few non-trivial VB6 programs do not make use of ActiveX libraries in addition to those preinstalled in Windows. The obvious examples are the control libraries that provide all but the intrinsic VB6 controls. These normally require registration, but since Windows XP there has been a way to use them without registration. This isn't directly supported by VB6, and the VB6 IDE/compiler and tools do not provide any assistance in doing so.
Even if you post-processed your application for reg-free COM and marked everything to run from file shares it is still a poor idea. Your application will require far more memory to run because everything must be resident the entire run.
As already stated above, this just isn't a good idea.
I will But ALl OCX And DLL Files on the application Folder But WithOut Installing The Application So How to register all dll and Ocx From my Vb6 CodeQuote:
Originally Posted by Conroy Vanderbluff
In practical terms there are no Windows machines that do not have the VB6 runtimes. I even have a Win95 OSR2 VM for program testing that had the necessary runtime files either out of the box or after I had installed IE 5.x as part of initial system setup.
Do not do this!Quote:
Originally Posted by dawoud66
It can wreak all kinds of havoc, breaking other applications on the machine. These kinds of libraries have designated places they must be installed in, "installing" them requires creating or incrementing usage counters in the registry, etc.
Just create a proper installer and use that.
Agreed, use an installer and install the program on all the computers then create a shortcut to the one on the network and all clients can use the same exe, once installed you can make changes/updates to the exe on the server and everyone will be able to use it without issue so long as you haven't added new controls or dlls references to the project since it was installed.
If you want it simple to where you don't need to install it on the client PCs then you need to write the program in such a way that it does not use any external OCX, Dlls beyond what would already be present on all the client computers.
But that has almost all of the problems of what was requested in the first place, the biggest being high network traffic and crashes due to network interruptions.
The way I do it is having an installer for all the needed runtimes which need to be registered and/or copied to the system directory.
This installation package is then installed on all (needed) client PCs.
The actual executable can then be placed on a network share. As long as you don't change the external components your application relies on, then you can update this executable as often as you need.
I don't see how starting the executable from the network can cause networking conflicts and/or crashes.
The problem is that as the program runs Windows does overlaying. This means as memory is required Windows throws away segments of code, since when needed they can be re-read from disk. If the program is on a remote file share that means network traffic, and if the network experiences a momentary interruption it means a program crash.
I really never experienced this and we have a dozen application running on/from big network shares.
It is one of those things that may work "most of the time" but isn't correct operation.
You can lead a horse to water... as they say.
One of my customers has 10 clients running the exe from the shared drive on the server. (This was the way they wanted it)
The program has been in use 5 days a week 8 hours a day for 14 years and counting, never had any issues
Another client tried this and had major issues, horrible lag and had to be changed. The culprit in that case was Citrix and an improper network design. Way to much traffic on the WAN
But Citrix Not Free Program so the Customer Must Pay MoreQuote:
Originally Posted by DataMiser
I don't think you understood what I posted, In the case where the customer had problems it was because they were using Citrix and dod not have the network setup correctly. Citrix was using so much bandwidth that there was very little left for the program I had written causing it to be very slow at times.
The customer thought it was my software even though I had told them they had a network issue, fortunately for me the day I had to go there the Citrix system went down and they could see that my program was actually very fast when citrix wasn't hogging the network.
Anyway the bottom line is that you really should not do this, and definitely don;t do it just to try and avoid a little work with the install. Your software will work better if it is installed and ran locally from the client computers. If you must install on the network then the results will vary based on how large your program is, what it does and more importantly network speed and how much network traffic exists on the network
Many Thanks For All And I will Not Do that