| PDOX 7 on Win03 Term Serv, OPLOCKS =0 not wrking|
I moved a paradox 7 app from one working TS Win2003 server to another TS Win2003. On the new server, it acted as if Oplocks was enabled, regardless of registry oplock settings. The settings I am using are below along with a more complete descripion of the new server setup. Does anyone know of other Oplock related registry or TS settings I could try?
When I have multiple users accessing the same table, users do not see each other's edits. With User A and B in the table, User A edits and closes the table, B doesn't see A's edits, makes new conflicting edits closes the table and wipes out A's Edits. I get the same result if install and run PDOXRT11.
I got this installation working by moving the data from the TS D:\ partition to another fileserver on the same network. My assumption is the TS server is not handling oplocks related function as intended, but the file server is.
The new server: IBM XSeries_335, Win 2003 SP2 setup for a TS role, only three ...
I tried Mike's suggestion of System|Init|LocalShare = True and that does seem to resolve the problem on this server.
I think there is more to it because even with the LocalShare = False, this same app runs fine on a different terminal server.
The problematic server was converted from a file server to an Application Server by someone else, and I think that allowed different handling of opplocks or similar. I have several installs on termin...