A customer had to run a RBASE 4.5 (!) application on a new IT environment, a Win2012R12 terminalserver with Win7 virtual desktops. They start a DOS box which calls rbase.exe using batch file. Problem: First rbase client modify shared server.sy5 file as expected, but does not set free this file until the DOS-session is closed. Other RBASE clients are not able to modify server.sy5 anymore, so they are not able to connect. On classical network they hadn't this problem.
Somebody has an idea about this problem? Some hints for settings at terminal server? And yes, customer has already bought RBG10 of course. He's working on migration from this 24 year old 4.5 to version 10, but need some more time. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
