Can I install 32-bit OE Studio on the database server without destroying the 64-bit RDBMS installation? It currently seems like I will need two sets of application code, one server side in 64-bit r-code and one client side in 32-bit, is this correct? How do we run batches in shared memory on the server? _progres.exe does not seem to want to run anything, every startup procedure I try throws an error even _desk.r which is bundled with the 圆4 RDBMS install. OE Studio will not install which means we need to compile from a development server which pushes compile time up to 6 hours when it took only 40 minutes on the database server in shared memory (this simply seems down to the horse power difference between an enterprise specced server and a developer PC). How do we compile and run r-code on the server for batches? Only the RDMS license can be installed from the 64-bit Progress install file.

This has worked fantastically for nearly 7 years, but now needs upgrading to 10.2B before the 32-bit database limits are reached. All machines including the server use the same set of compiled code, clients get access to it via a network share and it is run locally in shared memory for batches on the server. One set of application code is compiled on the server running the database. Client is run from a desktop shortcut calling prowin32.exe. The application itself is relatively basic, it runs as a simple client/server (no AppServers) with both GUI and CHUI client screens.

Does anyone have any deployment advice for how to get the database running on Windows 2008R2 SP1 圆4 and the clients to remain on XP? We are still in the test phase, but live deployment is scheduled for Easter this year. Both client and server OS is Windows, currently XP for clients and 2003 for database server. We are upgrading a site from 9.1D09 x86 to 10.2B05 圆4.

Progress openedge 10.2b download