Hi,

I think the question is not only data file but structure as well.

Problems:
Storage of lists
Logs
Preferences

Regards,

Wayne


Wayne Stewart
about.me/waynestewart




On 12 January 2017 at 13:09, Spencer Hinsdale <[email protected]> wrote:
> The v15 R4 Upgrade docs show features to store the Data File Path in User 
> Prefs, etc...
>
> ftp://ftp-public.4d.fr/Documents/Products_Documentation/LastVersions/Line_15R4/VIntl/4D_Upgrade_v15_R4.pdf
>  
> <ftp://ftp-public.4d.fr/Documents/Products_Documentation/LastVersions/Line_15R4/VIntl/4D_Upgrade_v15_R4.pdf>
>
>
> In v15 it is possible to set compatibility to allow read-only (to suppress 
> the error) and then in code determine if the "default" data file is being 
> opened, read your own prefs, and Open Data File (last saved to your prefs).
>
>
>> On Jan 11, 2017, at 5:36 PM, John DeSoi <[email protected]> wrote:
>>
>> Hi Piotr,
>>
>>
>>> On Jan 11, 2017, at 4:55 AM, Piotr Chabot Stadhouders 
>>> <[email protected]> wrote:
>>>
>>> So, my question is (again) :
>>> Does anybody know of a way to run an application build with 4D Volume 
>>> Desktop in a write protected citrix environment, without using virtual 
>>> store and elevated privileges?
>>> Now, in v15, I am getting an alert saying "Database is write protected". 
>>> Because 4D still wants to store the location of the datafile in the 
>>> structure?
>>> I thought this was possible in v15
>
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to