RPWin.ini interfering with Χ# app (RPro 3.0)
Posted: Tue Apr 09, 2024 8:46 am
Hello all!
In VO we didn't have any RpWin.ini to deal with, so this is new to us. Suddently while testing our X# apps we realised that some date properties used to change suddently from 99-99-9999 to 99-99-99 in all date controls. Also other properties like SetEpoch were changed to 1900 etc.
We thenm realised that this happened after any printing with Report Pro. When loading, previewing or/and printing a report via X# app, an RpWin.ini file is created at the Working Directory. Then the date field specification of the app is changed according to the rpwin.ini settings.
Is there a way not to have an rpwin.ini to X# apps?
We set these global variables hardcoded with functions such as SetCentury, SetEpoch etc.
We want to avoid distributing an Rpwin.ini to our applications.
At VO apps when using Report Pro 3.9 there wasn’t something like this.
Also where can we find a documentation concerning RPWin.ini?
Thanks in advance.
In VO we didn't have any RpWin.ini to deal with, so this is new to us. Suddently while testing our X# apps we realised that some date properties used to change suddently from 99-99-9999 to 99-99-99 in all date controls. Also other properties like SetEpoch were changed to 1900 etc.
We thenm realised that this happened after any printing with Report Pro. When loading, previewing or/and printing a report via X# app, an RpWin.ini file is created at the Working Directory. Then the date field specification of the app is changed according to the rpwin.ini settings.
Is there a way not to have an rpwin.ini to X# apps?
We set these global variables hardcoded with functions such as SetCentury, SetEpoch etc.
We want to avoid distributing an Rpwin.ini to our applications.
At VO apps when using Report Pro 3.9 there wasn’t something like this.
Also where can we find a documentation concerning RPWin.ini?
Thanks in advance.