thank you both

Gunther.. I didn't know about the "keep connection alive" thing

Tom.. local share OFF?

Tom.. what complications come from the combination of local / TS access?

--

Steven Green
Myrtle Beach, South Carolina, USA

http://www.OasisTradingPost.com

Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Tom Krieg"  wrote in message news:5e130189$1@pnews.thedbcommunity.com... 

In my experience, if you're running a Paradox app completely under 
terminal server and only the TS server is hitting the tables, there's no 
need to do anything. The users will need to have local sharing turned to 
OFF on their BDE.

That's if all data accss to tables is via the Terminal Server. And keep 
in mind my experience with Paradox on TS finished with Windows Server 
2012 R2.

On 4/01/2020 2:08 am, Steven Green wrote:
> does anyone have any definitive rules or concepts for current 
> win10/Server, for oplocks and write caching?
> 
> on top of the usual errors and issues, I'm seeing "unknown internal 
> operating error" and "unknown share violation", which seem to go away if 
> you reboot the server, and a lot of strange error message from Tutility, 
> including "version mismatch"
> 
> sometimes I see errors like this on the terminal server side only, 
> sometimes from the "local" connections, too.. rebooting the server in 
> the middle of the day isn't actually up there on the list of things I 
> like to do (sigh)
> 
> -- 
> 
> Steven Green
> Myrtle Beach, South Carolina, USA
> 
> http://www.OasisTradingPost.com
> 
> Collectibles and Memorabilia
> Vintage Lego Sets and Parts
> - and Paradox support, too