settings Posts

I have a terminal server installation that has been running paradox 11 runtime.  All users on this installation access paradox through the terminal server. After running fine for the initial four months, I recently ran into a curuption problem that looked a lot like the old Oplocks of NT days or Terminal User settings of Win TS server 2003. I could watch two users viewing the same table, the edits of user A would not appear for user B after user A committed the edits and the table would get immediately currupted.  It looked to me that both users were holding the tables in memory and not committing changes to disk until the user left the table.  A single user could function normally in the application without curruption.  I tried a lot of things on that server to try to fix it including oplocks and terminal user reg edits, but I couldn't correct the problem. I recovered the entire server from a month old backup, prior to the start of the problem, install...

Posted to MB Topic: Paradox Runtime & Distribution « Paradox Board

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 ...

Posted to MB Topic: Paradox Setup, Vista, etc. « Paradox Board

I dual boot WinXP Pro X32 and Windows 7 X64 Pro on separate drives and run Paradox 11 from WP Office X3 on both.  I mostly use XP and  there are no problems with Pdox after those updates but when I went to use it under Windows 7 today the Project Viewer showed no files in the working directory. Until now there was no problem with the Windows 7 installation.  I uninstalled and reinstalled Pdox and then tried to set Project Viewer to the proper working directory and it crashes.  I've tried this several times.  If I open a table with Explorer Pdox will start and open it but if I try Project Viewer it crashes.  I went to check the BDE settings but I can't seem to find BDE in the control panel or anywhere else in Windows 7.

Posted to MB Topic: Paradox Setup, Vista, etc. « Paradox Board