Hi Fabio
During a devcon in USA a few years back the VFP gang at Microsoft had a session where they wanted to hear suggestions from the attendees, and I had a suggestion which is related.
I suggested that for all the commands which were dependent of the SAFETY settings, they should add a new parameter, for instance NOSAFETY which would take presedence if it was specified. Like COPY TO FILE XX NOSAFETY to always copy even if the target file already exists, and SAFETY is ON. Like it is now, you have to write relatively many lines of code to do many such simple tasks.
>Hi Gregory,
>
>----------
>I would not bother making a wish if I were you: (1) It's only one extra SET in your SetDataSession() program, and (2) you cannot rely on the registry when you distribute an application, ie I feel safer having a prog that sets all the datasession values even if I have to call it explicitely every time.
>----------
>
>I'm agree with you, by my idea is this:
>for any VFP datasession SET add a Clause DEFAULT.
>
>SET SAFETY OFF DEFAULT
>SET MULTILOCKS ON DEFAULT
>SET DELETED ON DEFAULT
>SET TALK OFF DEFAULT
>SET CENTURY ON DEFAULT
>SET DATE TO GERMAN DEFAULT
>SET HOURS TO 24 DEFAULT
>SET DECIMALS TO 6 DEFAULT
>SET POINT TO ',' DEFAULT
>....
>....
>
>
>With this i run it when app start, change the dafault value for any new datasession, and then i can skip the SetDatasession call
>( it is simple and sure ) for any new datasession.
>
>Fabio
