Hi Tom,

You are correct. It is known that the BDE treats the idapi.cfg 
differently when it is set to read only just like it does when it is on 
Terminal Server (and FYI when it is on CDROM).

We have never shared the cfg file - in fact we ship it just about empty 
and set everything at runtime.

FWIW
Leslie.


On 28/06/2018 7:24 PM, Tom Krieg wrote:
> Actually, I've been sharing IDAPI32.cfg for over 20 years (starting with
> Win95 and Novell Netware). The trick is to put it in a folder outside
> Program Files and to make it ReadOnly. As I understand it, IDAPI32.cfg
> contains the BDE parameters and doesn't get updated by users in their
> day-to-day operations. You define a different IDAPI32.cfg file with the
> -O Paradox command line switch.
>
> Her problem may have something to do with the "Windows 10 update 1803
> broke my network connections" problem. Intel NIC card drivers (not all)
> are removed from the computer and the drivers need to be manually
> re-installed. Something to do with an .inf file being deleted by the
> update.
>
> https://www.techrepublic.com/article/how-to-resolve-network-problems-caused-by-the-windows-10-april-2018-update/
>
>
>
> Leslie wrote on 28/06/2018 4:30 PM:
>> First thing to know is that the idapi.cfg was never designed to be
>> shared across a mapped drive (Terminal Server is a different situation).
>>

---
This email has been checked for viruses by AVG.
https://www.avg.com