I can't create an installation package because I was asked to develop a standalone application to be used in a LAN. My app must reside on the server and on each workstation there will only be a link to it.

Since the VB5 basic runtimes are already present in the operating system (as of Windows 98), I don't need a setup package to make my app work.

The problem may arise if I make use of OCX's or any third-party DLLs which may need to be registered in the Windows Registry in order to work.

Nevertheless, I found that the registration of an OCX (such as MSFlexGrid) can be performed automatically by your software (without any setup package) if you just place the library in the app folder instead of the System32 directory.

Before releasing my software in the LAN of my school, I would like to be sure that there will be no conflict generated by MSFlexGrid if a newer version of that OCX is already present on a workstation.This will prevent me from cutting a very poor figure. (Other software of mine has always run like clockwork so far.)