Server 5.0 and 5.1 on same machine

Both Server 5.0 and 5.1 can be on the same server but you have to make sure that your application is picking up the run-time files from the correct location.

The best way to do this is to link your programs as dynamic so it will use the system registry entries to locate the install folder of the correct Server product.

If your programs are linked as shared only then it will search the PATH to find the run-time system, cblrtss.dll and if the Server 5.0 is in the PATH then it will pick up the wrong version.

So either use dynamic run-time system linking or ensure that your PATH is pointing to the Server 5.1\\bin folder and that there are no stray old versions of cblrtss.dll within your PATH.

Also make sure that the Server 5.1 is upgraded to the same wrappack level as your Net Express product.

Thanks.

I have a COBDIR system variable  wich folder had MFFH.DLL CBLVIOS.DLL CBLRTSS.DLL and CBLINTS.dll all with 5.0 versions.

- Replaced them with 5.1 versions

- Removed the 5.0\\bin from PATH variable (leaving only 5.1)

That still didn't work with my programs compiled as static; only when i compiled them as Shared- Dynamic. Is this setup correct? If not, what can i improve here?

I have a COBDIR system variable  wich folder had MFFH.DLL CBLVIOS.DLL CBLRTSS.DLL and CBLINTS.dll all with 5.0 versions.

- Replaced them with 5.1 versions

- Removed the 5.0\\bin from PATH variable (leaving only 5.1)

That still didn't work with my programs compiled as static; only when i compiled them as Shared- Dynamic. Is this setup correct? If not, what can i improve here?

Programs linked as static should not be affected by this as the run-time system is linked into the .EXE directly so it does not load the cblrtss.dll from disk.

What error are you getting on statically  link executables?

Is it the same error?

The whole idea of the dynamic linking is so the run-time system will be found in its original installed location using the registry entries for the Server product.

If you are copying the run-time .dlls to different locations and setting COBDIR or PATH to point to them then that is defeating the purpose.

To use this effectively you should build all of your programs as shared dynamic (both 5.0 and 5.1) and then allow this mechanism to search for the required run-time filles using only the install folders, removing any other copies of the run-time files that may exist on your computer.

Thanks.